From: "Hannes Domani via gdb-patches" <gdb-patches@sourceware.org>
To: Gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH v2 1/2] Display ExceptionRecord for $_siginfo
Date: Sat, 08 Feb 2020 21:09:00 -0000 [thread overview]
Message-ID: <955533175.395475.1581196161533@mail.yahoo.com> (raw)
In-Reply-To: <83r1z4dehn.fsf@gnu.org>
Am Samstag, 8. Februar 2020, 21:13:54 MEZ hat Eli Zaretskii <eliz@gnu.org> Folgendes geschrieben:
> > From: Simon Marchi <simark@simark.ca>
> > Date: Sat, 8 Feb 2020 15:00:10 -0500
> >
> > > Program received signal SIGSEGV, Segmentation fault.
> > > main () at crasher.c:4
> > > 4 *(int*)0x123 = 0;
> > > (gdb) p $_siginfo
> > > $1 = {
> > > ExceptionCode = 3221225477,
> > > ExceptionFlags = 0,
> > > ExceptionRecord = 0x0,
> > > ExceptionAddress = 0x401632 <main+18>,
> > > NumberParameters = 2,
> > > ExceptionInformation = {1, 291, 0 <repeats 13 times>}
> > > }
> > > (gdb) p/x $_siginfo.ExceptionCode
> > > $2 = 0xc0000005
> > > (gdb) p/x $_siginfo.ExceptionInformation[1]
> > > $3 = 0x123
> > >
> > > And 0xc0000005 is the value of EXCEPTION_ACCESS_VIOLATION.
> > >
> > > [1] https://docs.microsoft.com/en-us/windows/win32/api/winnt/ns-winnt-exception_record
> >
> > Eli, could you please comment on this from a Windows user point of view, if this looks
> > correct to you?
>
> LGTM, although I'd prefer to have ExceptionCode be printed in hex by
> default. But I guess that could be tricky, and the next patch makes
> then print as symbolic names anyway.
These were basically the same thoughts I had when I made this.
> > Also, does this need a manual/NEWS update?
>
>
> I think only NEWS, because the manual already says "on some targets",
> and gives an example from GNU/Linux only.
Is it fine if I add the following to this patch?:
* NEWS: Mention $_siginfo support for Windows.
---
diff --git a/gdb/NEWS b/gdb/NEWS
index d4e2e70f38..c202fe06de 100644
--- a/gdb/NEWS
+++ b/gdb/NEWS
@@ -10,6 +10,9 @@
that support it (see entry for GDB 9, below), providing faster
performance for programs with many symbols.
+* The $_siginfo convenience variable now also works on Windows targets,
+ and will display the EXCEPTION_RECORD of the last handled exception.
+
* New commands
set exec-file-mismatch -- Set exec-file-mismatch handling (ask|warn|off).
next prev parent reply other threads:[~2020-02-08 21:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200208162614.4918-1-ssbssa.ref@yahoo.de>
2020-02-08 16:26 ` Hannes Domani via gdb-patches
2020-02-08 16:26 ` [PATCH v2 2/2] Use enums for human-readable exception information Hannes Domani via gdb-patches
2020-02-08 20:04 ` Simon Marchi
2020-02-08 20:15 ` Eli Zaretskii
2020-02-08 20:00 ` [PATCH v2 1/2] Display ExceptionRecord for $_siginfo Simon Marchi
2020-02-08 20:13 ` Eli Zaretskii
2020-02-08 21:09 ` Hannes Domani via gdb-patches [this message]
2020-02-09 3:28 ` Eli Zaretskii
2020-02-09 5:33 ` Simon Marchi
2020-02-09 11:19 ` Hannes Domani via gdb-patches
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=955533175.395475.1581196161533@mail.yahoo.com \
--to=gdb-patches@sourceware.org \
--cc=ssbssa@yahoo.de \
/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