From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 183AD3858C31; Wed, 15 Feb 2023 21:34:27 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 183AD3858C31 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1676496867; bh=EleFgNDPXsnZpfliFzqsPnDazTYN7iO7VtwVIOA3+5A=; h=From:To:Subject:Date:In-Reply-To:References:From; b=lOSmmi7nq+ynbzuBfLkL7ME4tbE2kxmq6TnghUAHf8nhe5hvgSpjTJYHzIiZ6r6dm gJZFlEbPi/VCE5/NV/szskdb8ODIQM6YIbwvasvHIAXdwrhoyoO9LuMQ6yW3H/+F41 4XftxLqnUFA9JnlPp4SAnzL0bprXWkCsiFYknZ3g= From: "pedro at palves dot net" To: gdb-prs@sourceware.org Subject: [Bug remote/15297] CTRL-C with set debug remote often crashes GDB Date: Wed, 15 Feb 2023 21:34:25 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: remote X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: pedro at palves dot net X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: jan at jankratochvil dot net X-Bugzilla-Target-Milestone: 14.1 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: target_milestone bug_status resolution 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=3D15297 Pedro Alves changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|--- |14.1 Status|ASSIGNED |RESOLVED Resolution|--- |FIXED --- Comment #7 from Pedro Alves --- > However, running Jan's test, on current master reveals we still have prob= lems=20 > with a Ctrl-c coming in while Python code is running: > ... > > That "^CPython Exception 'KeyboardInterrupt'>: " is probably from the Python frame unwinder machin= ery. > At that point the target has the terminal, and since=20 > 2f99e8fc9cb84ca80cfca6c119f1f22bbfd2a314 this should not have happened (C= hange=20 > SIGINT handler for extension languages only when target terminal is ours)= , but=20 > something's still not right over there. I suspect that it's because now= =20 > remote.c uses the standard SIGINT handler, which calls set_quit_flag, whi= ch=20 > calls active_ext_lang->ops->set_quit_flag. So I think this issue is finally fixed by this series: https://inbox.sourceware.org/gdb-patches/20230210233604.2228450-1-pedro@pal= ves.net/T/#m79098ae4ed85a49c9693a47a0ad7a139f63d47dd There's a separate PR about Ctrl-C and Python unwinder during execution: https://sourceware.org/bugzilla/show_bug.cgi?id=3D26266 which is really the same thing, and I'm leaving that open, hoping for a testcase. So we can close this one. --=20 You are receiving this mail because: You are on the CC list for the bug.=