From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id B7CDF3858C83; Thu, 1 Dec 2022 09:50:24 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org B7CDF3858C83 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1669888224; bh=M5EFgn92toAPvIm1k3erft9EFkmBYFrIbi6HKNj7Jl8=; h=From:To:Subject:Date:In-Reply-To:References:From; b=DQd5WgFFWSlAz5hkYunar0awm24QJuNTolF3iKjrDCCdE5hfIJ1aroyQcYZRTVxGx lDy0IGbn2J7ZEGHOD4p6IFVY3c8D7RoG9AGZnvEmZSjg7wOrzzyzN5pe2PagjAxkIg f/M7kZ8Y8q8HXyleazKKYaaV/IvxWte1faQbbWmY= From: "vries at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug gdb/29833] [gdb] FAIL: gdb.server/monitor-exit-quit.exp: monitor exit Date: Thu, 01 Dec 2022 09:50:23 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: vries at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://sourceware.org/bugzilla/show_bug.cgi?id=3D29833 --- Comment #4 from Tom de Vries --- 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. --=20 You are receiving this mail because: You are on the CC list for the bug.=