Yes. I've also seen crashes on non-conditional breakpoints. I literally save before any test run. Then at suitable junctures I intercept savestack (+ controlKey down) to write the stack out as Json + script only stack and commit it all to my VCS.
But again I haven't (yet) noticed a pattern with these things. I did notice that the remote debugger prevents all IDE stack breakpoints from working until the app is closed on a test device. For a long time I couldn't understand why breakpoints had stopped working and why no-one else was having this problem. Then finally it struck me that there may only be a small group of us using remote debugger (+ Android). On Wed, Sep 8, 2021 at 8:50 PM Ben Rubinstein via use-livecode < use-livecode@lists.runrev.com> wrote: > > And while we're confessing laziness, my more shameful confession is about > a > crashing bug when using conditional breakpoints. I've become used to being > very wary as soon as I start using these, and saving very often. Have > others > seen this issue? > > _______________________________________________ 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