From: Tom Tromey <tom@tromey.com>
To: Simon Marchi via Gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Replace deprecated_target_wait_hook by observers
Date: Thu, 23 Sep 2021 14:10:10 -0600 [thread overview]
Message-ID: <87o88j3vfh.fsf@tromey.com> (raw)
In-Reply-To: <8240f04b-eef9-f14b-1d1f-18b2a187cc65@polymtl.ca> (Simon Marchi via Gdb-patches's message of "Tue, 7 Sep 2021 11:08:03 -0400")
>>>>> "Simon" == Simon Marchi via Gdb-patches <gdb-patches@sourceware.org> writes:
Simon> The only dangerous things about this is if an observer throws an
Simon> exception, an exception will exit the destructor, and that aborts the
Simon> process.
I think observers generally aren't supposed to throw.
If we want gdb to robust against this, I think the thing to do would be
add a try/catch in observable::notify.
Tom
next prev parent reply other threads:[~2021-09-23 20:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-26 14:40 Patrick Monnerat
2021-09-04 11:58 ` [PING] " Patrick Monnerat
2021-09-07 15:08 ` [PATCH] " Simon Marchi
2021-09-23 20:10 ` Tom Tromey [this message]
2021-10-25 19:02 ` Simon Marchi
2021-10-27 18:39 ` Tom Tromey
2022-03-12 12:41 patrick
2022-03-14 13:53 ` Tom Tromey
2022-03-14 14:16 ` Patrick Monnerat
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=87o88j3vfh.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).