From: Pedro Alves <pedro@palves.net>
To: Tom de Vries <tdevries@suse.de>, gdb-patches@sourceware.org
Cc: Simon Marchi <simon.marchi@polymtl.ca>
Subject: Re: [PATCH v2] [gdb] Fix heap-use-after-free in select_event_lwp
Date: Mon, 26 Feb 2024 15:28:41 +0000 [thread overview]
Message-ID: <414f42f2-577e-4393-a1da-8f1741a55662@palves.net> (raw)
In-Reply-To: <8d111966-a623-4c84-86bf-d48ff4efbeb9@suse.de>
On 2024-02-26 14:23, Tom de Vries wrote:
> On 2/23/24 15:33, Pedro Alves wrote:
>> With that, it makes a lot more sense to me.
>>
>> So, here's the same patch but now with an adjusted commit log, with that
>> missing info added. WDYT?
>>
>
> Hi Pedro,
>
> I've verified that the scenario is as you describe it.
>
> LGTM.
>
Great, thanks for the verification. I'm merging it now.
Pedro Alves
prev parent reply other threads:[~2024-02-26 15:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-23 11:48 Tom de Vries
2024-01-23 16:08 ` Simon Marchi
2024-01-23 17:52 ` Tom de Vries
2024-02-09 15:46 ` Pedro Alves
2024-02-19 15:04 ` Tom de Vries
2024-02-21 17:42 ` Pedro Alves
2024-02-22 11:43 ` Tom de Vries
2024-02-23 14:33 ` Pedro Alves
2024-02-26 14:23 ` Tom de Vries
2024-02-26 15:28 ` Pedro Alves [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=414f42f2-577e-4393-a1da-8f1741a55662@palves.net \
--to=pedro@palves.net \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@polymtl.ca \
--cc=tdevries@suse.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).