Author Topic: How does Run abort work  (Read 8796 times)

Offline tigerbeard

  • Almost regular
  • **
  • Posts: 186
Re: How does Run abort work
« Reply #15 on: April 05, 2016, 11:49:01 pm »
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.

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 13413
    • Travis build status
Re: How does Run abort work
« Reply #16 on: April 06, 2016, 12:05:12 am »
Have you found your problem with the exceptions switch enabled?
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

Offline tigerbeard

  • Almost regular
  • **
  • Posts: 186
Re: How does Run abort work
« Reply #17 on: April 06, 2016, 12:30:36 am »
With the exceptions enabled the debugger triggers on the crash. And that even in the double C::B setup with attached dbg. Quite cool  8)

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!