From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id CFD08385841C; Wed, 10 Jan 2024 20:58:53 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org CFD08385841C DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1704920333; bh=bekmFil3vrbbv6aqd9lOe5i9UnUNwJVgRy53EKJs9/U=; h=From:To:Subject:Date:In-Reply-To:References:From; b=dOdJ8yNape9NOtj1RWawJyZdq4HlgquWr3JB7+UHa8kMRD1tudT21VzzZ7xctAGqB 6lGvMotvBbJ3NjtIW0LVeeDZnpSdrV4zWjslSEFnMjQBS34nswsGYEejLWjb/3y4Wg DIWiBXY2wIjOqOe1rzTLHk3P6Kf4BNwclHW/5OM0= From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug symtab/24820] .debug_names has incorrect contents Date: Wed, 10 Jan 2024 20:58:53 +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: unknown 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: tromey 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=3D24820 --- Comment #13 from Tom Tromey --- One last note about the size and whatnot. To my mind, one of the biggest problems with DWARF is that it is very difficult to read. The new scanner, which has acceptable-ish performance, was a pretty big effort and we're still tracking down the occasional data race (since threading was the only way to make it really fast). However, this situation seems absurd to me. DWARF is hard to read -- but this is due to decisions made in the design, not really anything intrinsic to the problem area. That is, DWARF gives us abbrevs and a generically hierarchical structure, when really gdb (and IMO debuggers in general) wants something different. In theory this stuff can be used for other things, but in practice this approach means optimizing for these hypothetical other uses at the expense of the 90% use case. So, rather than putting effort into an index, whether it be .gdb_index or .debug_names, it would be much better to tackle this at the source and make reading cheap and easy. (This btw is why I put off .debug_names so long, I just had trouble getting myself over the feeling that I was working on the wrong end of the problem.) This is partly the idea of CTF, though they went the C-only route and also didn't really integrate into gdb very well. --=20 You are receiving this mail because: You are on the CC list for the bug.=