From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 0C1D43858C20; Thu, 23 Mar 2023 10:44:09 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 0C1D43858C20 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1679568250; bh=ouLBM6CZBSka7UBe9U9LLcMUnyEoBMsY3XTqj2lZlvQ=; h=From:To:Subject:Date:In-Reply-To:References:From; b=aENdRteKeeqH13g07+dn8m3eRioZP/1nu2gAcI1jeGg90f/paPiVGd7poIeY2EIi5 eQr+wbWe5c1GChXUeKn3iW9vXpLP/SqgUP3CKizZdLtzuTYenkHFdLMkXaeWQ5YC9Q Kg+DbafdH41YoddQlJ2AyELffOVYldEfeI3q5QsQ= From: "vries at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug symtab/30265] [gdb/symtab] info var shows incorrect file/line combination for static const class member Date: Thu, 23 Mar 2023 10:44:09 +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: vries at gcc dot gnu.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=3D30265 --- Comment #2 from Tom de Vries --- I already did commit 99d679e7b30 ("[gdb/symtab] Fix "file index out of rang= e" complaint") to fix a problem with this commit, which limits the scope of the original fix. On current master, if I do: ... diff --git a/gdb/dwarf2/read.c b/gdb/dwarf2/read.c index c9208a097bf..b1934d26af7 100644 --- a/gdb/dwarf2/read.c +++ b/gdb/dwarf2/read.c @@ -7610,7 +7610,7 @@ handle_DW_AT_stmt_list (struct die_info *die, struct dwarf2_cu *cu, then there won't be any interesting code in the CU, but a check later= on (in lnp_state_machine::check_line_address) will fail to properly excl= ude an entry that was removed via --gc-sections. */ - if (have_code) +// if (have_code) dwarf_decode_lines (cu->line_header, cu, lowpc, decode_mapping); } ... so effectively going back to the behaviour from before commit 6d263fe46e0, = the regression disappears (not helpfully, with the current state of the test-ca= se, the regression disappearing is shown by PASS -> FAIL, a problem that was already reported here: https://sourceware.org/pipermail/gdb-patches/2023-March/198210.html). So, at first glance it looks like the scope of the fix needs to be reduced = even further. --=20 You are receiving this mail because: You are on the CC list for the bug.=