From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 2BBAB3891C1B; Mon, 20 Nov 2023 13:56:52 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 2BBAB3891C1B DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1700488612; bh=adU+cd/n7roDtSb+iqSj1txqOqpfink2V72F9laKCjA=; h=From:To:Subject:Date:In-Reply-To:References:From; b=um26LjmnGIuNMVWHTvejaX9FUEE64xaTTzHXi/rgRYe0VSkwBTQ+VM5OxxaFpCc9Y 4SHs/xx1frzjj0UMb+CYijLkfIbPqreLQDUXtD0y9WZj/gkNfhsifv8icvlFHWG62X 4naiTG0pgmIpQ9Fdexp8IIWW9SVF3RQM1PrrDBQY= From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug gdb/31073] Inconsistent Variable Values: Discrepancy between Source-Level and Instruction-Level Debugging Date: Mon, 20 Nov 2023 13:56:51 +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: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: tromey at sourceware dot org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: NOTABUG 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=3D31073 Tom Tromey changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tromey at sourceware dot o= rg --- Comment #4 from Tom Tromey --- (In reply to Anonymous from comment #3) > (In reply to Tom de Vries from comment #1) > > Inconsistencies between source-level debugging and instruction-level > > debugging is not a bug. >=20 > Hi Tom,=20 >=20 > I still have some concerns regarding the information provided by the > debugger, as it may be somewhat misleading. From the user's perspective, = it > appears that lines 27 and 28 have indeed been executed, yet the variable > values remain unchanged. Consequently, I am curious if there are any > assurances or guarantees from the compiler or debugger. Normally for this sort of thing, the debugger is at the mercy of the compiler. If this is a concern to you, what you should try is digging into the location expressions for these variables. If they do cover all the intermediate PCs, then perhaps it is a compiler bug. --=20 You are receiving this mail because: You are on the CC list for the bug.=