From: Andreas Schwab <schwab@linux-m68k.org>
To: Tom Tromey <tromey@redhat.com>
Cc: Pedro Alves <pedro@codesourcery.com>, gdb-patches@sourceware.org
Subject: Re: RFC: add table headers to "info thread" output
Date: Sat, 25 Dec 2010 19:23:00 -0000 [thread overview]
Message-ID: <m21v55eo19.fsf@whitebox.home> (raw)
In-Reply-To: <m3sjxr3ptw.fsf@fleche.redhat.com> (Tom Tromey's message of "Tue, 21 Dec 2010 12:09:47 -0700")
Tested on ppc-linux and checked in as obvious.
Andreas.
2010-12-25 Andreas Schwab <schwab@linux-m68k.org>
* gdb.threads/thread-specific.exp (get_thread_list): Update.
* gdb.threads/execl.exp: Update.
Index: gdb.threads/execl.exp
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/gdb.threads/execl.exp,v
retrieving revision 1.4
diff -u -a -p -r1.4 execl.exp
--- gdb.threads/execl.exp 21 Dec 2010 19:10:15 -0000 1.4
+++ gdb.threads/execl.exp 25 Dec 2010 17:52:30 -0000
@@ -57,11 +57,11 @@ gdb_test "info threads" ".*" "info threa
set test "info threads after exec"
gdb_test_multiple "info threads" "$test" {
- -re "2 Thread .*$gdb_prompt $" {
+ -re "2 *Thread .*$gdb_prompt $" {
# Old threads left behind.
fail "$test"
}
- -re "4 Thread .*$gdb_prompt $" {
+ -re "4 *Thread .*$gdb_prompt $" {
# New threads registered.
fail "$test"
}
Index: gdb.threads/thread-specific.exp
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/gdb.threads/thread-specific.exp,v
retrieving revision 1.13
diff -u -a -p -r1.13 thread-specific.exp
--- gdb.threads/thread-specific.exp 18 Jun 2010 17:44:40 -0000 1.13
+++ gdb.threads/thread-specific.exp 25 Dec 2010 17:52:30 -0000
@@ -44,11 +44,14 @@ proc get_thread_list { } {
-re "New Thread \[^\n\]*\n" {
exp_continue
}
- -re "^\\* *(\[0-9\]*) Thread \[^\n\]*main\[^\n\]*\n" {
+ -re "^ *Id *Target Id\[^\n\]*\n" {
+ exp_continue
+ }
+ -re "^\\* *(\[0-9\]*) *Thread \[^\n\]*main\[^\n\]*\n" {
set thr_list "$expect_out(1,string) $thr_list"
exp_continue
}
- -re "^ *(\[0-9\]*) Thread \[^\n\]*\n" {
+ -re "^ *(\[0-9\]*) *Thread \[^\n\]*\n" {
lappend thr_list $expect_out(1,string)
exp_continue
}
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2010-12-25 17:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-20 21:50 Tom Tromey
2010-12-21 4:01 ` Joel Brobecker
2010-12-21 9:39 ` Pedro Alves
2010-12-21 19:10 ` Tom Tromey
2010-12-25 19:23 ` Andreas Schwab [this message]
2010-12-27 8:20 ` Andreas Schwab
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=m21v55eo19.fsf@whitebox.home \
--to=schwab@linux-m68k.org \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.com \
--cc=tromey@redhat.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