From: Tom Tromey <tom@tromey.com>
To: Andrew Burgess <aburgess@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb/testsuite: another attempt to fix gdb.threads/thread-specific-bp.exp
Date: Fri, 15 Dec 2023 12:21:52 -0700 [thread overview]
Message-ID: <87il4z6zlb.fsf@tromey.com> (raw)
In-Reply-To: <1576cabe99ace298caa833800f40781be8404682.1701513033.git.aburgess@redhat.com> (Andrew Burgess's message of "Sat, 2 Dec 2023 10:31:04 +0000")
>>>>> "Andrew" == Andrew Burgess <aburgess@redhat.com> writes:
I didn't see a response to this.
Andrew> I think the easiest solution here is just to have the
Andrew> gdb_test_multiple contain two patterns, each pattern consists of the
Andrew> two parts, but in the alternative orders, thus, for a particular
Andrew> output configuration, only one regexp will match. With this change in
Andrew> place, I no longer see the intermittent failure.
Makes sense to me.
Approved-By: Tom Tromey <tom@tromey.com>
Tom
next prev parent reply other threads:[~2023-12-15 19:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-02 10:31 Andrew Burgess
2023-12-15 19:21 ` Tom Tromey [this message]
2023-12-18 11:16 ` Andrew Burgess
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=87il4z6zlb.fsf@tromey.com \
--to=tom@tromey.com \
--cc=aburgess@redhat.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).