From: Tom Tromey <tom@tromey.com>
To: Lancelot SIX via Gdb-patches <gdb-patches@sourceware.org>
Cc: Lancelot SIX <lancelot.six@amd.com>, lsix@lancelotsix.com
Subject: Re: [PATCH] gdb/testsuite: fix gdb.threads/linux-dp.exp regex
Date: Fri, 07 Oct 2022 13:12:50 -0600 [thread overview]
Message-ID: <871qrjtpl9.fsf@tromey.com> (raw)
In-Reply-To: <20221007142104.261240-1-lancelot.six@amd.com> (Lancelot SIX via Gdb-patches's message of "Fri, 7 Oct 2022 15:21:04 +0100")
>>>>> "Lancelot" == Lancelot SIX via Gdb-patches <gdb-patches@sourceware.org> writes:
Lancelot> The regex for this test accounts for different situations (with /
Lancelot> without debug symbol) but assumes that if debug info is present the
Lancelot> backtrace shows execution under pthread_create. However, for the
Lancelot> implementation under test, we are under start_thread.
Lancelot> Update the regex to accept start_thread.
Looks good to me. Thank you.
Tom
next prev parent reply other threads:[~2022-10-07 19:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-07 14:21 Lancelot SIX
2022-10-07 19:12 ` Tom Tromey [this message]
2022-10-07 19:18 ` Lancelot SIX
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=871qrjtpl9.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=lancelot.six@amd.com \
--cc=lsix@lancelotsix.com \
/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).