Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Manoj Iyer <manjo@austin.ibm.com>
To: gdb-patches@sources.redhat.com
Subject: [RFC] switch-threads.exp added tests.
Date: Tue, 14 Jun 2005 19:46:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.58.0506141408560.17509@lazy> (raw)


I added couple of tests to explicitly test switching threads. Any
comments/suggestion?


2005-06-14  Manoj Iyer  <manjo@austin.ibm.com>

	* gdb.base/switch-threads.exp: Added test explicitly changing threads.

--------------------------------------------------------------
--- ./switch-threads.exp	2003-10-09 14:49:28.000000000 -0500
+++ /tmp/switch-threads.exp	2005-06-14 14:01:15.000000000 -0500
@@ -24,8 +24,6 @@
 # multi-threaded stubs to reliably get this correct; gdbserver defaulted
 # to the first thread.

-# TODO: we should also test explicitly changing threads with the "thread"
-# command.

 if $tracelevel then {
 	strace $tracelevel
@@ -49,4 +47,7 @@ runto_main
 gdb_breakpoint thread_func
 gdb_continue_to_breakpoint "continue to thread_func"
 gdb_test "next" ".*foo \\(\\);"
-
+gdb_test "info threads" "\\* .*2 Thread.*.LWP.* .*thread_func.*"
+gdb_test "thread 1" ".*Switching to thread 1.*"
+gdb_test "next" ".*foo \\(\\).*\[0-9\]*"
+gdb_test "thread 2" ".*Switching to thread 2.*"

-----
manjo
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+ Cogito ergo sum                                                          +
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++


             reply	other threads:[~2005-06-14 19:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-14 19:46 Manoj Iyer [this message]
2005-06-14 19:50 ` Daniel Jacobowitz

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=Pine.LNX.4.58.0506141408560.17509@lazy \
    --to=manjo@austin.ibm.com \
    --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