From: Tom Tromey <tromey@adacore.com>
To: Tom Tromey via Gdb-patches <gdb-patches@sourceware.org>
Cc: Tom Tromey <tromey@adacore.com>
Subject: Re: [PATCH] Check for listeners in emit_exiting_event
Date: Wed, 15 Jun 2022 13:51:12 -0600 [thread overview]
Message-ID: <87wndhwvrj.fsf@tromey.com> (raw)
In-Reply-To: <20220603164619.1861019-1-tromey@adacore.com> (Tom Tromey via Gdb-patches's message of "Fri, 3 Jun 2022 10:46:19 -0600")
>>>>> "Tom" == Tom Tromey via Gdb-patches <gdb-patches@sourceware.org> writes:
Tom> I noticed that emit_exiting_event does not check whether there are any
Tom> listeners before creating the event object. All other event emitters
Tom> do this, so this patch updates this one as well.
I'm checking this in now.
Tom
prev parent reply other threads:[~2022-06-15 19:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-03 16:46 Tom Tromey
2022-06-15 19:51 ` Tom Tromey [this message]
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=87wndhwvrj.fsf@tromey.com \
--to=tromey@adacore.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).