>
> 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 0x40000015 to 0x80000003.
That would mean that when not under debugger, user would have no idea
what has happened and why his process just disappeared. I recommend to
use __debugbreak()/DebugBreak() only when being debugged. Fortunately,
Win32API has a function for detecting that:
if(IsDebuggerPresent())
__debugbreak();
else
abort();
(I use similar construction in my assert-like macros for my projects and
I can confirm it really makes my debugging experience much easier.)
Morous
------------------------------------------------------------------------------
Get 100% visibility into Java/.NET code with AppDynamics Lite!
It's a free troubleshooting tool designed for production.
Get down to code-level detail for bottlenecks, with <2% overhead.
Download for free and get started troubleshooting in minutes.
http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk
_______________________________________________
Mingw-w64-public mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
