[Bug gdb/26614] New: UNRESOLVED: gdb.multi/multi-target.exp: continue: non-stop=on: inferior 5
vries at gcc dot gnu.org
sourceware-bugzilla@sourceware.org
Mon Sep 14 14:50:37 GMT 2020
https://sourceware.org/bugzilla/show_bug.cgi?id=26614
Bug ID: 26614
Summary: UNRESOLVED: gdb.multi/multi-target.exp: continue:
non-stop=on: inferior 5
Product: gdb
Version: HEAD
Status: NEW
Severity: normal
Priority: P2
Component: gdb
Assignee: unassigned at sourceware dot org
Reporter: vries at gcc dot gnu.org
Target Milestone: ---
[ On x86_64 laptop, with openSUSE Leap 15.2. ]
With this patch (not sure yet whether it's relevant) in place:
...
diff --git a/gdb/testsuite/lib/gdbserver-support.exp
b/gdb/testsuite/lib/gdbserver-support.
exp
index a2cc80f28d..7b9c0eef6e 100644
--- a/gdb/testsuite/lib/gdbserver-support.exp
+++ b/gdb/testsuite/lib/gdbserver-support.exp
@@ -451,8 +451,10 @@ proc gdbserver_exit { is_mi } {
# We use expect rather than gdb_expect because
# we want to suppress printing exception messages, otherwise,
# remote_expect, invoked by gdb_expect, prints the exceptions.
+ set read_prompt 0
expect {
-i "$gdb_spawn_id" -re "$gdb_prompt $" {
+ set read_prompt 1
exp_continue
}
-i "$server_spawn_id" eof {
@@ -463,6 +465,7 @@ proc gdbserver_exit { is_mi } {
warning "Timed out waiting for EOF in server after
$monitor_exit"
}
}
+ gdb_assert {$read_prompt}
}
}
close_gdbserver
...
and running in parallel with:
...
$ stress -c 5
...
I ran into:
...
(gdb) PASS: gdb.multi/multi-target.exp: continue: non-stop=on: inferior 2
Remote debugging from host ::1, port 34088^M
Process build/gdb/testsuite/outputs/gdb.multi/multi-target/multi-target
created; pid = 8649^M
monitor exit^M
(gdb) Killing process(es): 8649^M
PASS: gdb.multi/multi-target.exp: continue: non-stop=on: $read_prompt
ERROR: GDB process no longer exists
GDB process exited with wait status 8627 exp14 0 0 CHILDKILLED SIGABRT SIGABRT
UNRESOLVED: gdb.multi/multi-target.exp: continue: non-stop=on: inferior 5
...
--
You are receiving this mail because:
You are on the CC list for the bug.
More information about the Gdb-prs
mailing list