From: Simon Marchi <simark@simark.ca>
To: Eli Zaretskii <eliz@gnu.org>, Hannes Domani <ssbssa@yahoo.de>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH v2 1/2] Display ExceptionRecord for $_siginfo
Date: Sun, 09 Feb 2020 05:33:00 -0000 [thread overview]
Message-ID: <d7ccb9d5-85a2-4d2c-6710-cb7196fae490@simark.ca> (raw)
In-Reply-To: <83o8u8cuda.fsf@gnu.org>
On 2020-02-08 10:28 p.m., Eli Zaretskii wrote:
>> Date: Sat, 8 Feb 2020 21:09:21 +0000 (UTC)
>> From: "Hannes Domani via gdb-patches" <gdb-patches@sourceware.org>
>>
>> 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
>
> Yes, this sounds good to me, thanks.
Thanks for chiming in Eli.
So Hannes, just to be clear, you can go ahead and push this series, thanks!
Simon
next prev parent reply other threads:[~2020-02-09 5:33 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
2020-02-09 3:28 ` Eli Zaretskii
2020-02-09 5:33 ` Simon Marchi [this message]
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=d7ccb9d5-85a2-4d2c-6710-cb7196fae490@simark.ca \
--to=simark@simark.ca \
--cc=eliz@gnu.org \
--cc=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