How does Run abort work

[tigerbeard]

Do you have catching of exception enabled in the debugger settings.
If it crashes because of the way cb is killing the app then the debugger should catch it.

If the bug disappears when the debugger is attached to the app then you have either a timing/threading related bug or uninitialized memory/use-after-free bug.

Cool. Thats the kind of thing I was looking for. I did not have exceptions enabled.

[oBFusCATed]

Have you found your problem with the exceptions switch enabled?

[tigerbeard]

With the exceptions enabled the debugger triggers on the crash. And that even in the double C::B setup with attached dbg. Quite cool 

It took me into very final wxLog shutdown. That is matching the cause I had found before (see previous post)
So indeed, with that enabled before I would have saved me a couple of hrs searching!