I found later that the same thing was happening away from this code block, and with just a red breakpoint.
As I don't restart my PC for weeks on end, I quit LC and restarted. Both of these strange error situations disappeared. Which suggests that it is some complex condition (either within my app or within the IDE) that leads to this situation. On Fri, Jul 17, 2020 at 5:09 PM Ludovic THEBAULT via use-livecode < use-livecode@lists.runrev.com> wrote: > > > > Le 17 juil. 2020 à 13:52, Bernard Devlin via use-livecode < > use-livecode@lists.runrev.com> a écrit : > > > > This is mystifying in so many ways. I've seen this a few times and I'm > at > > a loss to explain it. It's LC 9.5.1 on Windows 10. > > > > *When the code gets to the above breakpoint, the debugger exits to top. > It > > takes about 3 seconds with the debugger sitting at the breakpoint before > > the engine exits to top.* > > > > Hello, > > I've already had the same behavior but I noticed that it happens when > there is an error in the executed code (but an error that doesn't block the > execution of the script !). By fixing the script, the breakpoint then works > as it should. > > Maybe there is an error in your script (before the code you displayed > here). > > Ludovic > _______________________________________________ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your > subscription preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode > _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
