Remote debugger error message
paul at researchware.com
Sun Jul 2 15:19:05 EDT 2023
I got this error in a new install of LC969 on a brand new Windows 11 HP
After I quit LC and started it again, I have not seen the error. I think
there may have been some Windows notification that appeared but went
away before I could do anything in the standard Win10/11 Notifications
(lower right corner) and when I, later, popped open the notification
panel, there was nothing there.
I have now launched LC many times since without seeing the error again.
On 7/2/2023 3:08 PM, J. Landman Gay via use-livecode wrote:
> I've seen the same error more than once but it's a bit random and I
> don't know what triggers it. It's only in the IDE so far, even though
> I've included the remote debugger in the standalone. Funny that it
> should occur in the IDE when the remote debugger isn't active.
> The remote debugger in the standalone did trigger some errors a few
> times. Maybe something is left in memory? The IDE was still running
> while testing the standalone.
> On 7/2/23 1:24 PM, David Epstein via use-livecode wrote:
>> panagiotis m asked:
>> How do you trigger this error? Could you provide a recipe?
>> With the stacks that trigger the error it is hard to troubleshoot
>> them without triggering the error. So I’m starting with an entirely
>> new stack, and will report if I encounter the problem.
>> I suspect the problem has something to do with a message that calls a
>> handler in a stack-in-use.
>> Best wishes,
>>> On Thu, Jun 29, 2023 at 8:40?PM David Epstein via use-livecode
>>> <use-livecode at lists.runrev.com
>>> <mailto:use-livecode at lists.runrev.com>> wrote:
>>>> I?ve just started using LiveCode 9.6.9 and 10.0.0 DP 5 on two Intel
>>> Macs, and can do very little without getting this error message:
>>>> ?There was an error executing a script in stack
>>> com.livecode.library.remotedebugger. No more information is available
>>> because the stack is password protected.?
>> use-livecode mailing list
>> use-livecode at lists.runrev.com
>> Please visit this url to subscribe, unsubscribe and manage your
>> subscription preferences:
More information about the use-livecode