This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: How to debug fatal exceptions on Windows?
- From: Eli Zaretskii <eliz at gnu dot org>
- To: Pierre Muller <pierre dot muller at ics-cnrs dot unistra dot fr>
- Cc: gdb at sourceware dot org
- Date: Tue, 06 Aug 2013 19:07:16 +0300
- Subject: Re: How to debug fatal exceptions on Windows?
- References: <83y58evno4 dot fsf at gnu dot org> <"000001ce92bb$ff059a60$fd10cf20$ at muller"@ics-cnrs.unistra.fr>
- Reply-to: Eli Zaretskii <eliz at gnu dot org>
> From: "Pierre Muller" <pierre.muller@ics-cnrs.unistra.fr>
> Date: Tue, 6 Aug 2013 17:45:36 +0200
>
> 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.
>
>
> Did you try to run gdb on itself and
> place a breakpoint on the location of the FirstChance code?
If I do that, and the breakpoint breaks, how will I be able to see
which code in the application (Emacs) caused the exception?
Or did you mean something else?
Thanks.