From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 9429C3858C31; Fri, 16 Feb 2024 02:42:03 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 9429C3858C31 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1708051323; bh=nG/d5dNBeACFdnC+v3JFNz6IoQM92LOVuJQcTXryWpU=; h=From:To:Subject:Date:In-Reply-To:References:From; b=fCHX+T5y2gpbOa0a3taaH8l6Hpiqpz4Oq46pbfL3XTGAr7Dv/9q9lu3RXvT1cVnQs Jqdeb4xB0wtN64WqpqjNIVug49UyiQ8+yeUSVWM8799YZUxKCNgqYu8JcrLvaJcOco Z992KV3NLC8KwVEbUS0HvixqXN0SlrRmTyp9hw5w= From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug symtab/30728] [gdb/symtab, cc-with-dwz] FAIL: gdb.cp/breakpoint-locs.exp: break N1::C1::baz Date: Fri, 16 Feb 2024 02:42:02 +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: tromey at sourceware 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=3D30728 --- Comment #18 from Tom Tromey --- (In reply to Tom Tromey from comment #17) > What I'd propose is having the .debug_names entry written > as referring to the DIE in the PU, but emit the CU as the > "canonical" includer... except when the DIE is an inline > function, in which case all CUs must be listed. >=20 > This would have also be documented as a gdb extension, because > DWARF seems to ignore this issue. When re-reading an index like this, we'll end up with a different data structure than the one we started out with, which seems unfortunate. That is, the scanner will end up with the per-CU data having "includer" links, but the debug-names reader will just know that function "xyz" appears in CUs 1/2/3, if that makes sense. It'd be nicer to have a single data structure, but then we're limited by what .debug_names can represent. --=20 You are receiving this mail because: You are on the CC list for the bug.=