Re: [Mingw-w64-public] Usability improvement: add debug breaks to abort() calls

2013-08-10 Thread LRN
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10.08.2013 17:25, Martin Mitáš wrote: >> >> The difference between using abort() and using a debug break is that >> debug break, if it goes unhandled, won't print the usual "requrested to >> terminate blahblahblah" stuff, and the exception code that

Re: [Mingw-w64-public] Usability improvement: add debug breaks to abort() calls

2013-08-10 Thread Martin Mitáš
> > The difference between using abort() and using a debug break is that > debug break, if it goes unhandled, won't print the usual "requrested to > terminate blahblahblah" stuff, and the exception code that WER shows > will change from 0x4015 to 0x8003. That would mean that when not under

Re: [Mingw-w64-public] Usability improvement: add debug breaks to abort() calls

2013-08-10 Thread Erik van Pienbroek
LRN schreef op do 08-08-2013 om 12:23 [+0400]: > This is mostly a usability change. I, personally, really don't like when > a program i'm debugging suddenly dies for no reason. > > Opinions? I would really welcome such a change. In the past we've already stumbled across this issue with Qt5 (and w

[Mingw-w64-public] Usability improvement: add debug breaks to abort() calls

2013-08-08 Thread LRN
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 abort() is a msvcr(t) function, and it does not throw an exception, just prints a message and terminates your program. Well, actually, it does call SIGABRT handler before terminating. But that's in-program, and isn't known to the debugger. And most lib