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] Change py-thread-exited.exp to work with gdbserver
Date: Thu, 10 Aug 2023 11:42:15 -0600 [thread overview]
Message-ID: <871qga3ibs.fsf@tromey.com> (raw)
In-Reply-To: <20230731173254.2725820-1-tromey@adacore.com> (Tom Tromey via Gdb-patches's message of "Mon, 31 Jul 2023 11:32:54 -0600")
>>>>> "Tom" == Tom Tromey via Gdb-patches <gdb-patches@sourceware.org> writes:
Tom> gdbserver does not notify gdb of new threads when they are created.
Tom> I'm not sure if this is documented anywhere, but it is mentioned on
Tom> this page:
Tom> https://sourceware.org/gdb/wiki/LocalRemoteFeatureParity
Tom> Search for "Finding new threads in the inferior".
Tom> This behavior is a bit unfortunate -- I would think that it would be
Tom> better to arrange for such notification if something on the gdb side
Tom> is interested.
Tom> Meanwhile, this patch fixes py-thread-exited.exp to work around this
Tom> problem.
Tom> Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=30677
I'm checking this in.
Tom
prev parent reply other threads:[~2023-08-10 17:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-31 17:32 Tom Tromey
2023-08-10 17:42 ` 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=871qga3ibs.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).