From: Philippe Waroquiers <philippe.waroquiers@skynet.be>
To: Pedro Alves <palves@redhat.com>, Mark Wielaard <mark@klomp.org>
Cc: gdb-patches@sourceware.org, Sergio Durigan Junior <sergiodj@redhat.com>
Subject: Re: [RFA] Fix GDB 8.3 regression crash when registers cannot be modified.
Date: Fri, 19 Apr 2019 12:37:00 -0000 [thread overview]
Message-ID: <1555677445.6208.15.camel@skynet.be> (raw)
In-Reply-To: <6bad9d21-3860-a7cf-5a5a-4d52ae139a43@redhat.com>
On Fri, 2019-04-19 at 12:48 +0100, Pedro Alves wrote:
> This version is OK.
Thanks for the review and the suggestion to use
std::uncaught_exception ().
Pushed to 8.3 branch.
Pushed an equivalent patch to master,
with TRY/CATCH/e.message replaced by try/catch/e.what ().
Philippe
next prev parent reply other threads:[~2019-04-19 12:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-13 8:28 Philippe Waroquiers
2019-04-19 11:04 ` Mark Wielaard
2019-04-19 11:36 ` Philippe Waroquiers
2019-04-19 11:49 ` Pedro Alves
2019-04-19 12:37 ` Philippe Waroquiers [this message]
2019-04-22 17:13 ` Sergio Durigan Junior
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=1555677445.6208.15.camel@skynet.be \
--to=philippe.waroquiers@skynet.be \
--cc=gdb-patches@sourceware.org \
--cc=mark@klomp.org \
--cc=palves@redhat.com \
--cc=sergiodj@redhat.com \
/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