From: Eli Zaretskii <eliz@gnu.org>
To: Simon Marchi <simark@simark.ca>
Cc: ssbssa@yahoo.de, gdb-patches@sourceware.org
Subject: Re: [PATCH v2 2/2] Use enums for human-readable exception information.
Date: Sat, 08 Feb 2020 20:15:00 -0000 [thread overview]
Message-ID: <83pneodefj.fsf@gnu.org> (raw)
In-Reply-To: <b2b73413-d189-62d4-6f82-3b5c03bcbd14@simark.ca> (message from Simon Marchi on Sat, 8 Feb 2020 15:04:23 -0500)
> From: Simon Marchi <simark@simark.ca>
> Date: Sat, 8 Feb 2020 15:04:23 -0500
>
> Eli, same question here. This makes GDB's EXCEPTION_RECORD type deviate from
> the official one, but just to improve readability when you print it. I think
> it's a good idea, but I'd like to hear what you think.
This LGTM.
> And again, should we document this behavior in the manual, or is it obvious and
> discoverable enough by itself (when the user prints $_siginfo, it should be
> self-explanatory, if they already know about the real EXCEPTION_RECORD type).
Only in NEWS, I think.
Thanks.
next prev parent reply other threads:[~2020-02-08 20:15 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 ` [PATCH v2 1/2] Display ExceptionRecord for $_siginfo 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 [this message]
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
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=83pneodefj.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=simark@simark.ca \
--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