Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: gdb-patches@sources.redhat.com
Subject: [RFA] New threads test
Date: Tue, 30 Sep 2003 19:22:00 -0000	[thread overview]
Message-ID: <20030930192158.GA5615@nevyn.them.org> (raw)

This is a test for the remote protocol issue I'm solving with vCont.  It
also shows up in schedlock, but the simpler test makes it much clearer
what's going wrong.  OK?

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer

2003-09-30  Daniel Jacobowitz  <drow@mvista.com>

	* gdb.threads/switch-threads.exp: New test.
	* gdb.threads/switch-threads.c: New source file.

--- /dev/null	1969-12-31 19:00:00.000000000 -0500
+++ testsuite/gdb.threads/switch-threads.c	2003-09-27 16:49:09.000000000 -0400
@@ -0,0 +1,25 @@
+#include <pthread.h>
+
+void foo (void)
+{
+}
+
+void *thread_func (void *arg)
+{
+  int x;
+  for (x = 0; x < 10; x++)
+    foo ();
+  return 0;
+}
+
+int main()
+{
+  pthread_t thr;
+  void *ret;
+  int x;
+
+  pthread_create (&thr, NULL, thread_func, NULL);
+  pthread_join (thr, &ret);
+  for (x = 0; x < 10; x++)
+    foo ();  
+}
--- /dev/null	1969-12-31 19:00:00.000000000 -0500
+++ testsuite/gdb.threads/switch-threads.exp	2003-09-28 13:04:48.000000000 -0400
@@ -0,0 +1,46 @@
+# Copyright (C) 2003 Free Software Foundation, Inc.
+
+# This program is free software; you can redistribute it and/or modify
+# it under the terms of the GNU General Public License as published by
+# the Free Software Foundation; either version 2 of the License, or
+# (at your option) any later version.
+# 
+# This program is distributed in the hope that it will be useful,
+# but WITHOUT ANY WARRANTY; without even the implied warranty of
+# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+# GNU General Public License for more details.
+# 
+# You should have received a copy of the GNU General Public License
+# along with this program; if not, write to the Free Software
+# Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA.  
+
+# Please email any bugs, comments, and/or additions to this file to:
+# bug-gdb@prep.ai.mit.edu
+
+# This file was written by Daniel Jacobowitz <drow@mvista.com>.
+#
+# It tests that the correct thread is single-stepped.
+
+if $tracelevel then {
+	strace $tracelevel
+}
+
+set testfile "switch-threads"
+set srcfile ${testfile}.c
+set binfile ${objdir}/${subdir}/${testfile}
+
+if {[gdb_compile_pthreads "${srcdir}/${subdir}/${srcfile}" "${binfile}" executable [list debug "incdir=${objdir}"]] != "" } {
+    return -1
+}
+
+gdb_exit
+gdb_start
+gdb_reinitialize_dir $srcdir/$subdir
+gdb_load ${binfile}
+
+runto_main
+
+gdb_breakpoint thread_func
+gdb_continue_to_breakpoint "continue to thread_func"
+gdb_test "next" ".*foo \\(\\);"
+


             reply	other threads:[~2003-09-30 19:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-30 19:22 Daniel Jacobowitz [this message]
2003-10-01 18:37 ` Michael Snyder
2003-10-01 18:52   ` Daniel Jacobowitz
2003-10-09 14:10     ` Daniel Jacobowitz
2003-10-09 19:41       ` Michael Snyder
2003-10-09 19:49         ` Daniel Jacobowitz
2003-10-10  0:05           ` Michael Snyder
2003-10-10  1:28             ` Daniel Jacobowitz
2003-09-30 19:39 Michael Elizabeth Chastain

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=20030930192158.GA5615@nevyn.them.org \
    --to=drow@mvista.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