From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id BE421385514E; Fri, 25 Nov 2022 12:55:06 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org BE421385514E DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1669380906; bh=7AoJ/tXQOyX0jw6HkvJAnEF98SJcXIu0utlq3Hsqeik=; h=From:To:Subject:Date:In-Reply-To:References:From; b=TNoY+zKmGsahm/0qofXx1V9Qn1CpnTgtm7CaWWdeNG3c4LZQ5YXapLv5dA0il2hxz OCZW2GpJR7z/LPRCpzmZPw2v8ZHyozuDazFHJP/BV6iX3O+u12YRWvBiF5f75dyTxv Ad+6iEFaMSnZbiHaGiOfVrh+KeD9dVEefk6gQrAo= From: "darius at dons dot net.au" To: gdb-prs@sourceware.org Subject: [Bug gdb/21221] gdb hangs while stepping an empty loop Date: Fri, 25 Nov 2022 12:55:06 +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: darius at dons dot net.au X-Bugzilla-Status: ASSIGNED 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: cc 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=3D21221 Daniel O'Connor changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |darius at dons dot net.au --- Comment #11 from Daniel O'Connor --- I just ran into this issue recently using a Black Magic probe to debug an S= TM32 and I think it is also a GDB bug. When this is triggered you have to kill GDB because ctrl-c does not interru= pt it. See this bug report: https://github.com/blackmagic-debug/blackmagic/issues/= 190 Notably GDB is not hung, nor is the BMP probe - GDB is simply stuck in a lo= op talking to the BMP setting breakpoints etc. I don't really know where to start looking in the GDB code to see why it bl= ocks being interrupted though so it's hard to see how difficult it would be to mitigate the problem. Obviously with the 'nop' work around it's not a big deal but it was quite a frustrating experience until I learnt that :) --=20 You are receiving this mail because: You are on the CC list for the bug.=