This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Fix MI/async testsuite
- From: Vladimir Prus <vladimir at codesourcery dot com>
- To: gdb-patches at sourceware dot org
- Date: Sun, 4 May 2008 16:18:14 +0400
- Subject: Fix MI/async testsuite
My previous patches to add =thread-created have broken MI testsuite
in async mode, since in async mode, the order of output is somewhat
different and the output for -exec-run is:
^running
=thread-created
(gdb)
with =thread-creating going before prompt, while in sync mode
(gdb) follows ^running immediately.
Fixed thusly.
- Volodya
Index: ChangeLog
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/ChangeLog,v
retrieving revision 1.1630
diff -u -p -r1.1630 ChangeLog
--- ChangeLog 4 May 2008 04:04:10 -0000 1.1630
+++ ChangeLog 4 May 2008 12:13:45 -0000
@@ -1,3 +1,8 @@
+2008-05-04 Vladimir Prus <vladimir@codesourcery.com>
+
+ * lib/mi-support.exp (mi_run_cmd): Allow for =thread-created
+ notification to appear.
+
2008-05-04 Daniel Jacobowitz <dan@debian.org>
* gdb.base/fullname.c: New file.
Index: lib/mi-support.exp
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/lib/mi-support.exp,v
retrieving revision 1.59
diff -u -p -r1.59 mi-support.exp
--- lib/mi-support.exp 30 Apr 2008 18:25:53 -0000 1.59
+++ lib/mi-support.exp 4 May 2008 12:13:45 -0000
@@ -821,7 +821,7 @@ proc mi_run_cmd {args} {
send_gdb "220-exec-run $args\n"
gdb_expect {
- -re "220\\^running\r\n${mi_gdb_prompt}" {
+ -re "220\\^running\r\n(=thread-created,id=\"1\"\r\n)?${mi_gdb_prompt}" {
}
timeout {
perror "Unable to start target"