I remember Joe saying that stepping “too fast” through the debugger results in crashes of the debugger. But - seriously - how fast is that? Click once every 10 seconds? This drives me nuts. I need to work through a lengthy algorithm. After clicking half a dozen up to a dozen times the debugger crashes EVERY TIME.
Is this so hard to reproduce for Xojo? How do you debug your own Xojo code?
Am I the only one to get those crashes? I’m using a Wacom tablet so I can click a bit faster than mouse users.
Intermittent crashes are about the worst things to isolate. It may also have something to do with your project or even your particular machine. If you can reproduce it, make sure you include a project in which you can and give very specific details about your hardware and software configuration.
For instance… You’re running 10.10, but Yosemite will run on machines manufactured all the way from 2011 through summer 2015.
Be sure to be aware of computed properties. If an error occurs in a getter, the app will crash when the debugger tries to display the result of the getter function. (I’ve been bitten by this more than a few times)
Could we have a setting to exclude computed properties from the “Values” pane?
Another source I’ve seen is the debug will crash if you are viewing the contents of a picture and step.
No viewing of anything special in the debugger. Just stepping through the code for some classes.
At least 10.9 and perhaps 10.8, too.
Can occur in any place of the code. I just need to have a complex piece of code and click a few times. Then I see the pizza of death and boom the debugger goes.
The project is about 450 classes.
I will try on the weekend with another computer. And also with a partial project.
Thats us deliberately stripping symbols and the fact that the crash logger simply grabs the nearest unstripped symbol + offset to report things.
Note the huge offset thats listed (35415)
Makes it harder for hackers to poke at
Its one of many things we have to do to combat pirates and general hacking at the framework
If its crashing in the framework there’s really nothing anyone but us can do with that information anyway
maybe. But we really like to have bugs fixed and the Xojo license checks should not be parts of the frameworks.
For other dev tools like Xcode or Visual Studio you can even get runtime in source code…
Which is exactly what I did 10 month ago. You already got a case that is 100% reproducible, it’s verified and everything.
<https://xojo.com/issue/33634>
Probably not the answer you’re looking for but …
I find that if I save right before debugging it doesn’t crash as often, and if I find a spot that I can’t step through b/c it will crash the debugger I only step a couple lines then resume with a break on the next line. Costs an extra 15 seconds to get to the next line but that’s cheaper than than the crash.
Stripping symbols doesn’t stop us from fixing bugs in the frameworks in the least
Submit the bug report with the log & we can deal with it on all platforms