From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 4AC2F3858C42; Sun, 7 Jan 2024 22:03:11 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 4AC2F3858C42 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1704664991; bh=CCjAThI2grhCSVqm22eNYtxOWHu5WHhGcusP8AOdPQg=; h=From:To:Subject:Date:In-Reply-To:References:From; b=rtevKalbFJP7LG2wkhX1LToyGYO5TRxFS2QfCIx59/04Jl2QrD5LuOgm4NX9FdlEQ nHnWEk+w0aXNPCdNBiUeNeszap/FpXgZwNF7i5K3YDLi0ykUTY9uXpfPGPpm9k0svD +c2XwLjJFd7gQRjTDrp6WqDfHn6O+Pv9gJqrgpnA= From: "peter0x44 at disroot dot org" To: gdb-prs@sourceware.org Subject: [Bug gdb/31194] Stepping on "int3" instruction fails assertion. Date: Sun, 07 Jan 2024 22:03:10 +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: peter0x44 at disroot dot 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=3D31194 --- Comment #11 from Peter0x44 --- A current workaround for this issue is to put a nop after the int3. I guess for this case, rip is still going to correspond to the same source line, so the assertion isn't a problem Changing the assert macro definition to: #define assert(e) do { if (!(e)) __asm__("int3; nop"); } while(0) has exactly the result I am looking for. I suppose this confirms the issue = is that rip is "off by one"? --=20 You are receiving this mail because: You are on the CC list for the bug.=