This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Fix FAIL: gdb.server/ext-attach.exp: detach
- From: Pedro Alves <pedro at codesourcery dot com>
- To: gdb-patches at sourceware dot org
- Date: Thu, 2 Apr 2009 23:41:05 +0100
- Subject: Fix FAIL: gdb.server/ext-attach.exp: detach
Just noticed this new failure when running the testsuite
on native x86_64-linux:
FAIL: gdb.server/ext-attach.exp: detach
Oops, since the gdb.server/ tests are skipped against
remote targets, one misses this when running the whole
testsuite against gdbserver.
This is not really a "failure", but an output change not
accounted for in the test:
-Detached from remote process.
+Detached from remote process 14483.
This difference happens because gdbserver now implements
the multiprocess extensions, and so GDB knows that it can
print the remote pid.
I've checked in the below adjustment to the test.
--
Pedro Alves
2009-04-02 Pedro Alves <pedro@codesourcery.com>
* gdb.server/ext-attach.exp: Expect an optional process id after
"Detached from remote process".
---
gdb/testsuite/gdb.server/ext-attach.exp | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Index: src/gdb/testsuite/gdb.server/ext-attach.exp
===================================================================
--- src.orig/gdb/testsuite/gdb.server/ext-attach.exp 2009-04-02 23:25:36.000000000 +0100
+++ src/gdb/testsuite/gdb.server/ext-attach.exp 2009-04-02 23:29:44.000000000 +0100
@@ -66,7 +66,7 @@ gdb_test "attach $testpid" "Attached to.
"attach to remote program 1"
gdb_test "backtrace" ".*main.*" "backtrace 1"
-gdb_test "detach" "Detached from remote process\\."
+gdb_test "detach" "Detached from remote process.*\\."
gdb_test "backtrace" "No stack\\." "backtrace with no program"
gdb_test "attach $testpid" "Attached to.*" \