From: Tom Tromey <tromey@adacore.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Tom Tromey <tromey@adacore.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] Ignore the last EXIT_THREAD_DEBUG_EVENT on Windows
Date: Thu, 27 Aug 2026 09:27:58 -0600 [thread overview]
Message-ID: <87zey7a8ht.fsf@tromey.com> (raw)
In-Reply-To: <86h5kmzoy1.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 22 Aug 2026 08:47:34 +0300")
Eli> Is there no possibility whatsoever that another thread will be created
Eli> while we handle the termination of what we consider to be "the last
Eli> thread"? Even though GDB supports scheduler-locking and non-stop mode
Eli> on Windows?
I don't see how it could, because at relevant point there are no other
threads in existence. So, there's nothing to run.
Anyway it's moot because I've approved a different patch for this bug.
Eli> Then this could be a problem due to effect of previous/other tests,
Eli> which run before or in parallel with this test.
It is not, because my testing was not done with the gdb test suite, but
with the AdaCore internal test suite, which does not have this problem.
In the AdaCore test suite, the tests are isolated from one another.
Tom
prev parent reply other threads:[~2026-08-27 15:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-21 16:18 Tom Tromey
2026-08-21 17:53 ` Eli Zaretskii
2026-08-21 18:18 ` Tom Tromey
2026-08-22 5:47 ` Eli Zaretskii
2026-08-27 15:27 ` 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=87zey7a8ht.fsf@tromey.com \
--to=tromey@adacore.com \
--cc=eliz@gnu.org \
--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