From: Pedro Alves <pedro@palves.net>
To: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH] New testcase gdb.threads/leader-exit-attach.exp (PR threads/8153)
Date: Fri, 12 Apr 2024 18:45:29 +0100 [thread overview]
Message-ID: <a4c0a14c-5651-41f9-bfab-6acaf91b852c@palves.net> (raw)
In-Reply-To: <be3bb9cb-a610-4284-b057-92c8ab43d046@palves.net>
On 2024-03-25 19:57, Pedro Alves wrote:
> Here's said testcase. Only two decades between original fix and testcase,
> not too bad. :-)
I've merged this one now.
prev parent reply other threads:[~2024-04-12 17:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-22 19:30 [PATCH] Fix windows_nat_target::fake_create_process ptid Pedro Alves
2024-03-23 6:39 ` Eli Zaretskii
2024-03-25 19:36 ` Pedro Alves
2024-03-25 19:57 ` [PATCH] New testcase gdb.threads/leader-exit-attach.exp (PR threads/8153) Pedro Alves
2024-03-26 15:26 ` Tom Tromey
2024-03-26 19:27 ` Pedro Alves
2024-03-26 20:04 ` Tom Tromey
2024-04-12 17:45 ` 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=a4c0a14c-5651-41f9-bfab-6acaf91b852c@palves.net \
--to=pedro@palves.net \
--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