[Bug gdb/29833] [gdb] FAIL: gdb.server/monitor-exit-quit.exp: monitor exit

["vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>]

https://sourceware.org/bugzilla/show_bug.cgi?id=29833

--- Comment #4 from Tom de Vries <vries at gcc dot gnu.org> ---
Sofar, I was not able to reproduce this other than by running the entire
testsuite, which is a bit unpractical.

I've tried the approach of adding debug logging, like so:
...
@@ -51,7 +51,18 @@ set gdbserver_protocol [lindex $res 0]
 set gdbserver_gdbport [lindex $res 1]
 gdb_target_cmd $gdbserver_protocol $gdbserver_gdbport

-gdb_test_no_output "monitor exit"
+gdb_test_no_output "set debug remote 1"
+gdb_test_no_output "set debug event-loop all"
+gdb_test_multiple "monitor exit" "" {
+    -re -wrap "Remote connection closed.*" {
+       fail $gdb_test_name
+    }
+    -re -wrap "" {
+       pass $gdb_test_name
+    }
+}
+gdb_test "set debug event-loop off"
+gdb_test "set debug remote 0"
 gdb_test_no_output "set confirm off"

 set do_cleanup 1
...

And after a entire testsuite run, I have:
...
(gdb) set debug remote 1^M
(gdb) PASS: gdb.server/monitor-exit-quit.exp: set debug remote 1
set debug event-loop all^M
(gdb) PASS: gdb.server/monitor-exit-quit.exp: set debug event-loop all
[event-loop] handle_file_event: invoking fd file handler `ui-1`^M
monitor exit^M
[remote] Sending packet: $qRcmd,65786974#d7^M
[remote] Packet received: OK^M
(gdb) PASS: gdb.server/monitor-exit-quit.exp: monitor exit
[event-loop] handle_file_event: invoking fd file handler `serial`^M
[remote] wait: enter^M
  [event-loop] clear_async_event_handler: clearing async event handler
`remote`^M
[remote] wait: exit^M
Remote connection closed^M
(gdb) PASS: gdb.server/monitor-exit-quit.exp: set debug event-loop off
[event-loop] handle_file_event: invoking fd file handler `ui-1`^M
set debug event-loop off^M
(gdb) set debug remote 0^M
(gdb) PASS: gdb.server/monitor-exit-quit.exp: set debug remote 0
...

AFAICT, the same behaviour reproduces, it just doesn't cause a fail, either
because of timing or because of less strict matching.

-- 
You are receiving this mail because:
You are on the CC list for the bug.