Sometimes the debugger is stable and then I get §$%& crashes every 5 minutes in an extended debugging session. Makes me rather frustrated. The crash is ALWAYS the same:
Thread 3 Crashed:
The greatest likelihood to trigger this crash is to view data in the debugger. But this is the purpose of a debugger. Does anyone have an idea how to reproduce this crash?
Mac OS 10.10.2, Xojo 2015r22.
Eli_Ott
June 3, 2015, 6:45am
2
I would start here with a BREAK at the top of this Constructor checking that all three arguments are valid:
@Eli : that was just an example crash log. WriteMailboxToDatabase works. The problems start at the line with DebuggerHook .
Eli_Ott
June 3, 2015, 9:11am
4
I very much doubt that. There must be something wrong before that, since the IDE running the application wants to step into the debugger if your code would not have any error it wouldn’t try that at this line with the number 10 in the crash log. And probably this thing being wrong is then also crashing the debugger.
@Eli : I very much doubt that because then pretty much EVERYTHING in my heavy duty algorithms would be wrong. I deal with large strings. This type of crash usually happens when I do
Debugging step by step through more than one class.
After viewing variables in the debugger.
WriteMailboxToDatabase isn’t much more than:
[code] if theExportOptions.ExportFormat = “Valentina” then
dim theWriter as new WriteMailboxToValentina(theMailbox, theArchive, theMailApplication)
Return theWriter.GetID
Else
Here are the relevant parts of the crash logs:
Thread 10 Crashed:
Thread 11 Crashed:
Thread 10 Crashed:
Thread 10 Crashed:
Thread 3 Crashed:
I’ve noticed similar crashes in the debugger (Windows) when I stepped through the code and want to check the values of some variables. It looks like the debugger has problems when the ‘debug stack’ becomes to complicated. Running the code without the debugger gives no problems, setting a stop somewhere, step through the code, look at some variables, sometimes a crash.
Could you upload the whole crash log somewhere?
@Joe : sure, here they are https://conbr.io/d/Q6XVFkoC . As Alain mentioned the deeper into the class hierarchy the likelier the crashes are.