From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id D6C5B3853567; Fri, 3 Feb 2023 10:23:24 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org D6C5B3853567 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1675419804; bh=VZYb58iurCM9/tSv5YVFOoR1IE5cBUDZ9CCn17x+j8A=; h=From:To:Subject:Date:In-Reply-To:References:From; b=JcpkqZmnwKwx2LKzJsp1rpXCgIeH9YgCsTKCaifxFZHqA9DMHgx3s/e/87RD99ag6 oV26Oqi7AGaNm5fON9ZOZ6XC0U1cGjshc9RsK/GaIWBFsQgrWNnMFDATxlPhW7Xsbq qne+iGwM4QehYe5+O+DKu8FRJZamQHJTSD4Jd/rE= 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, 03 Feb 2023 10:23:24 +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: 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 --- Comment #20 from Daniel O'Connor --- (In reply to Luis Machado from comment #19) > When it happens, can you actually interrupt it so you regain control of g= db? No, it's stuck sending this to the remote debugger: Breakpoint 1, i2c_write7_v1 (i2c=3D1073763328, addr=3D80, data=3D0x2001ffa4= "", n=3D2, start=3Dtrue) at hal.c:62 62 if (start) { (gdb) next 63 for (tout =3D I2C_TIMEOUT; tout > 0 && (I2C_SR2(i2c) & I2C_SR2_BUSY); tout--) (gdb) set debug remote 1 (gdb) next [remote] Sending packet: $Z1,8000546,2#7c [remote] Received Ack [remote] Packet received: OK [remote] Sending packet: $m800054e,2#61 [remote] Received Ack [remote] Packet received: 404b [remote] Sending packet: $m800054e,2#61 [remote] Received Ack [remote] Packet received: 404b [remote] Sending packet: $m8000550,2#2d [remote] Received Ack [remote] Packet received: 7b61 [remote] Sending packet: $m800054e,4#63 [remote] Received Ack [remote] Packet received: 404b7b61 [remote] Sending packet: $m800054e,2#61 [remote] Received Ack [remote] Packet received: 404b [remote] Sending packet: $m800054e,2#61 [remote] Received Ack [remote] Packet received: 404b [remote] Sending packet: $Z1,8000550,2#77 [remote] Received Ack [remote] Packet received: OK [remote] Sending packet: $c#63 [remote] Received Ack [remote] wait: enter [remote] wait: exit [remote] wait: enter [remote] Packet received: T05 [remote] select_thread_for_ambiguous_stop_reply: enter [remote] select_thread_for_ambiguous_stop_reply: process_wide_stop =3D 0 [remote] select_thread_for_ambiguous_stop_reply: first resumed thread is Thread 1 [remote] select_thread_for_ambiguous_stop_reply: is this guess ambiguou= s? =3D 0 [remote] select_thread_for_ambiguous_stop_reply: exit [remote] wait: exit (See https://github.com/blackmagic-debug/blackmagic/issues/190#issuecomment-1327= 190470) --=20 You are receiving this mail because: You are on the CC list for the bug.=