From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 2C9DE3858C30; Fri, 3 Feb 2023 10:32:19 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 2C9DE3858C30 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1675420339; bh=cmlteyA5Dr4Y65+y2cKb0vg6hZO6s2ahJkzQkhTjV8g=; h=From:To:Subject:Date:In-Reply-To:References:From; b=ctdjCZaQns5eoyDjQdZZf33zr08DVXz9HdrxogjBLSgdgXUcqQkgek/u41PrM5dF3 WcpDapejo3cd/+gH8HxKeIAdAHKulOkwZE4V+SoIm2gO4cH8ttXVlChHk50baXUF2g mWBsqrL7bP+vRxrMFofFIo+BaEXxAx3uJzJumguQ= From: "luis.machado at arm dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/21221] gdb hangs while stepping an empty loop Date: Fri, 03 Feb 2023 10:32:18 +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: luis.machado at arm dot com 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 #21 from Luis Machado --- Thanks for the input. That behavior sounds like a different bug in gdb. Whe= n in motion, gdb should always be interruptible so that you don't run into situations like this. There isn't much gdb can do about the tight loops themselves, but there sho= uld be a graceful way out of it with the interruption. In the past there used to be a race condition between gdb sending the inter= rupt request and the remote replying with a stop reply, and then gdb for some re= ason used to disregard the interrupt request and proceed with the motion (issuing stepi/continue over and over again). I'll have to play with this a bit more to see if I can reproduce the same situation. Unrelated, but I did notice the black magic debugging stub is still using A= CK packets though. If it isn't dealing with unreliable communication channels, that can be dropped. --=20 You are receiving this mail because: You are on the CC list for the bug.=