From: Pedro Alves <pedro@palves.net>
To: John Baldwin <jhb@FreeBSD.org>, Simon Marchi <simark@simark.ca>,
gdb-patches@sourceware.org
Subject: Re: [PATCH v3] gdb tests: Allow for "LWP" in thread IDs from info threads.
Date: Tue, 26 Mar 2024 12:19:30 +0000 [thread overview]
Message-ID: <076e4d7f-f6ca-4f4e-92e4-796dfdeaed19@palves.net> (raw)
In-Reply-To: <f29bb557-8e51-2bda-022f-08087af92458@FreeBSD.org>
On 2023-05-09 21:56, John Baldwin wrote:
> On 5/9/23 12:01 PM, Simon Marchi wrote:
>> And just one question:
>>
>>> diff --git a/gdb/testsuite/gdb.trace/report.exp b/gdb/testsuite/gdb.trace/report.exp
>>> index 14db2511d40..a5b7ccf4ba5 100644
>>> --- a/gdb/testsuite/gdb.trace/report.exp
>>> +++ b/gdb/testsuite/gdb.trace/report.exp
>>> @@ -380,7 +380,7 @@ proc use_collected_data { data_source } {
>>> # There is always a thread of an inferior, either a live one or
>>> # a faked one.
>>> - gdb_test "info threads" "\\* ${decimal} (process|Thread) \[0-9\.\]+\[ \t\].*"
>>> + gdb_test "info threads" "\\* ${decimal} ${tdlabel_re} \[0-9\.\]+\[ \t\].*"
>>
>> This one said "process" as well, I guess it's not important?
>
> Hummm, it didn't regress on Linux,
FYI, the tracepoint tests only run when testing against gdbserver.
I definitely see FAILs if "process" isn't matched:
$ make check RUNTESTFLAGS="--target_board=native-extended-gdbserver" TESTS="gdb.trace/report.exp"
...
Running /home/pedro/gdb/src/gdb/testsuite/gdb.trace/report.exp ...
FAIL: gdb.trace/report.exp: tfile: info threads
FAIL: gdb.trace/report.exp: ctf: info threads
prev parent reply other threads:[~2024-03-26 12:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-18 20:13 John Baldwin
2023-05-08 16:19 ` [PING] " John Baldwin
2023-05-09 19:01 ` Simon Marchi via Gdb-patches
2023-05-09 20:56 ` John Baldwin
2023-05-12 14:15 ` John Baldwin
2023-05-26 17:51 ` John Baldwin
2023-06-09 16:56 ` John Baldwin
2023-06-30 14:21 ` [PING] " John Baldwin
2023-07-14 15:35 ` John Baldwin
2024-03-22 20:58 ` John Baldwin
2024-03-26 12:19 ` 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=076e4d7f-f6ca-4f4e-92e4-796dfdeaed19@palves.net \
--to=pedro@palves.net \
--cc=gdb-patches@sourceware.org \
--cc=jhb@FreeBSD.org \
--cc=simark@simark.ca \
/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