How to debug fatal exceptions on Windows?

Eli Zaretskii eliz@gnu.org
Fri Aug 9 13:58:00 GMT 2013


> From: "Pierre Muller" <pierre.muller@ics-cnrs.unistra.fr>
> Date: Tue, 6 Aug 2013 17:45:36 +0200
> 
>   I could be that some "special" exception code is 
> used that is not understood by GDB.
>   In fact, an exception is send first to the debugger,
> then to the debuggee, and lastly again to the debugger if not handled by the
> debuggee.
> 
>   But if GDB does not recognize the exception code,
> it dies nothing on the first pass. 
> And the code is then caught by the gnu_exception_handler.

That is true, but it is unrelated to the issue I was having.  In the
use case I described, GDB was attached to Emacs when Windows already
displayed the "application needs to close" dialog.  At that point, the
search for exception handler already found the _gnu_exception_handler
function installed by the MinGW startup code, and called it.  The
problem is that the call stack down to the place that caused the
exception is not visible to GDB at this point.

So I think the possibility of GDB seeing an unknown exception on the
first chance call is not the problem here.



More information about the Gdb mailing list