From: Nick Roberts <nickrob@snap.net.nz>
To: Joel Brobecker <brobecker@adacore.com>,
Eli Zaretskii <eliz@gnu.org>,
gdb-patches@sources.redhat.com
Subject: Re: [PATCH] New annotation for threads
Date: Tue, 20 May 2008 16:43:00 -0000 [thread overview]
Message-ID: <18482.33700.236263.655308@kahikatea.snap.net.nz> (raw)
In-Reply-To: <18482.29129.410026.264704@kahikatea.snap.net.nz>
> I'll put it inside a function. I don't want to create a separate script
> because I think this test belongs with all the other tests for level 2
> annotations.
Like below.
--
Nick http://www.inet.net.nz/~nickrob
2008-05-20 Nick Roberts <nickrob@snap.net.nz>
* gdb.base/annota1.exp (thread_test): Test for new annotation.
--- annota1.exp 17 May 2008 21:09:09 +1200 1.29
+++ annota1.exp 20 May 2008 18:48:14 +1200
@@ -490,6 +490,45 @@ if [ regexp "core not found" $exec_outpu
}
}
+proc thread_test {} {
+ global objdir subdir srcdir
+ global gdb_prompt old_gdb_prompt
+ set testfile "watch_thread_num"
+ set srcfile ${testfile}.c
+ set binfile ${objdir}/${subdir}/${testfile}
+ set gdb_prompt $old_gdb_prompt
+
+ if { ![get_compiler_info ${binfile}] && [gdb_compile_pthreads "${srcdir}/${subdir}/${srcfile}" "${binfile}" executable {debug nowarnings}] == "" } {
+
+ gdb_exit
+ gdb_start
+ gdb_reinitialize_dir $srcdir/$subdir
+ gdb_load ${binfile}
+ if { ![runto main] } then {
+ fail "run to main"
+ return
+ }
+
+ set gdb_prompt \
+ "\r\n\032\032pre-prompt\r\n$gdb_prompt \r\n\032\032prompt\r\n"
+
+ send_gdb "set annotate 2\n"
+ gdb_expect {
+ -re "set annotate 2\r\n$gdb_prompt$" {}
+ }
+
+ send_gdb "next 2\n"
+ gdb_expect {
+ -re ".*\032\032new-thread" {
+ pass "new thread"
+ }
+ timeout { fail "new thread (timeout)" }
+ }
+ }
+}
+
+thread_test
+
# restore the original prompt for the rest of the testsuite
set gdb_prompt $old_gdb_prompt
next prev parent reply other threads:[~2008-05-20 7:54 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-18 16:06 Nick Roberts
2008-04-29 4:47 ` Joel Brobecker
2008-04-29 14:19 ` Nick Roberts
2008-05-01 18:18 ` Joel Brobecker
2008-05-01 18:44 ` Daniel Jacobowitz
2008-05-01 23:31 ` Nick Roberts
2008-05-01 23:37 ` Joel Brobecker
2008-05-02 0:07 ` Nick Roberts
2008-05-02 5:50 ` Joel Brobecker
2008-05-02 10:41 ` Eli Zaretskii
2008-05-17 15:51 ` Nick Roberts
2008-05-17 19:15 ` Stan Shebs
2008-05-17 21:18 ` Eli Zaretskii
2008-05-18 3:20 ` Bob Rossi
2008-05-18 9:11 ` Bob Rossi
2008-05-18 17:44 ` Eli Zaretskii
2008-05-19 8:48 ` Joel Brobecker
2008-05-19 9:09 ` Nick Roberts
2008-05-19 9:44 ` Eli Zaretskii
2008-05-19 12:39 ` Nick Roberts
2008-05-19 13:23 ` Eli Zaretskii
2008-05-20 15:27 ` Joel Brobecker
2008-05-20 16:10 ` Nick Roberts
2008-05-20 16:43 ` Nick Roberts [this message]
2008-05-20 18:09 ` Joel Brobecker
2008-05-21 3:55 ` Nick Roberts
2008-05-21 7:22 ` Joel Brobecker
2008-05-20 22:21 ` Eli Zaretskii
2008-05-20 22:54 ` Joel Brobecker
2008-05-21 3:26 ` Eli Zaretskii
2008-05-21 9:33 ` Joel Brobecker
2008-05-21 15:11 ` Nick Roberts
2008-05-21 15:14 ` Joel Brobecker
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=18482.33700.236263.655308@kahikatea.snap.net.nz \
--to=nickrob@snap.net.nz \
--cc=brobecker@adacore.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sources.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