From: Eli Zaretskii <eliz@gnu.org>
To: Pierre Muller <pierre.muller@ics-cnrs.unistra.fr>
Cc: gdb@sourceware.org
Subject: Re: How to debug fatal exceptions on Windows?
Date: Tue, 06 Aug 2013 16:07:00 -0000 [thread overview]
Message-ID: <83vc3ivm4r.fsf@gnu.org> (raw)
In-Reply-To: <"000001ce92bb$ff059a60$fd10cf20$@muller"@ics-cnrs.unistra.fr>
> 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.
next prev parent reply other threads:[~2013-08-06 16:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-06 15:34 Eli Zaretskii
2013-08-06 15:45 ` Pierre Muller
2013-08-06 18:50 ` Paweł Sikora
2013-08-06 19:25 ` Eli Zaretskii
[not found] ` <"000001ce92bb$ff059a60$fd10cf20$@muller"@ics-cnrs.unistra.fr>
2013-08-06 16:07 ` Eli Zaretskii [this message]
2013-08-09 13:58 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83vc3ivm4r.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb@sourceware.org \
--cc=pierre.muller@ics-cnrs.unistra.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox