public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug symtab/24820] .debug_names has incorrect contents Date: Wed, 10 Jan 2024 20:58:53 +0000 [thread overview] Message-ID: <bug-24820-4717-3ImRxQRkye@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-24820-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=24820 --- Comment #13 from Tom Tromey <tromey at sourceware dot org> --- 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. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2024-01-10 20:58 UTC|newest] Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-24820-4717@http.sourceware.org/bugzilla/> 2020-09-01 18:53 ` mark at klomp dot org 2021-02-18 16:27 ` tromey at sourceware dot org 2021-02-22 2:36 ` tromey at sourceware dot org 2021-02-22 8:55 ` fweimer at redhat dot com 2021-06-11 16:30 ` tromey at sourceware dot org 2022-04-22 18:03 ` tromey at sourceware dot org 2023-01-23 19:52 ` tromey at sourceware dot org 2023-12-03 0:07 ` tromey at sourceware dot org 2023-12-03 0:13 ` tromey at sourceware dot org 2023-12-03 0:16 ` tromey at sourceware dot org 2023-12-03 20:32 ` tromey at sourceware dot org 2023-12-04 14:19 ` tromey at sourceware dot org 2023-12-10 15:15 ` tromey at sourceware dot org 2023-12-10 15:16 ` tromey at sourceware dot org 2023-12-10 15:17 ` tromey at sourceware dot org 2023-12-10 15:21 ` tromey at sourceware dot org 2023-12-10 15:30 ` tromey at sourceware dot org 2024-01-10 2:01 ` tromey at sourceware dot org 2024-01-10 18:17 ` dblaikie at gmail dot com 2024-01-10 18:37 ` dblaikie at gmail dot com 2024-01-10 20:51 ` tromey at sourceware dot org 2024-01-10 20:58 ` tromey at sourceware dot org [this message] 2024-01-18 20:38 ` cvs-commit at gcc dot gnu.org 2024-01-18 20:38 ` tromey at sourceware dot org 2024-04-22 21:18 ` dblaikie at gmail dot com 2025-01-30 3:47 ` tromey at sourceware dot org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-24820-4717-3ImRxQRkye@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).