Remote debugger error message
J. Landman Gay
jacque at hyperactivesw.com
Sun Jul 2 15:08:35 EDT 2023
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:
Jacqueline Landman Gay | jacque at hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
More information about the use-livecode