From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 445C9385DC1C; Sat, 25 Apr 2020 09:42:40 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 445C9385DC1C From: "ricky at rzhou dot org" To: gdb-prs@sourceware.org Subject: [Bug symtab/25874] Printing variables after noreturn functions uses the wrong DWARF info Date: Sat, 25 Apr 2020 09:42:40 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: symtab X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: ricky at rzhou dot org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: DUPLICATE X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status resolution 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 X-BeenThere: gdb-prs@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gdb-prs mailing list List-Unsubscribe: , List-Archive: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Apr 2020 09:42:40 -0000 https://sourceware.org/bugzilla/show_bug.cgi?id=3D25874 Ricky Zhou changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #2 from Ricky Zhou --- Upon further reading, this looks like a duplicate of bug 25143 (see also the corresponding Clang bug, https://bugs.llvm.org/show_bug.cgi?id=3D39752). Looking at some of the discussion linked from the LLVM bug (http://lists.dwarfstd.org/pipermail/dwarf-discuss-dwarfstd.org/2018-Decemb= er/004500.html) it looks like the correctness of fudging PC values is much more controversi= al than I could have imagined! I now see that doing so does resolve the ambiguity between "right after the last instruction of a function" and "first instruction of the next function= ". *** This bug has been marked as a duplicate of bug 25143 *** --=20 You are receiving this mail because: You are on the CC list for the bug.=