From: Tom Tromey <tom@tromey.com>
To: Kevin Buettner <kevinb@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH v2] gdb/dwarf2: Add symbols for function declarations
Date: Fri, 05 Sep 2025 09:38:13 -0600 [thread overview]
Message-ID: <875xdwsye2.fsf@tromey.com> (raw)
In-Reply-To: <20250703194719.2254338-1-kevinb@redhat.com> (Kevin Buettner's message of "Thu, 3 Jul 2025 12:45:23 -0700")
>>>>> "Kevin" == Kevin Buettner <kevinb@redhat.com> writes:
Kevin> This version 2 commit
Kevin> adds that by making DW_TAG_subprogram declarations "interesting" to
Kevin> the indexer. The changes which do this are in gdb/dwarf2/abbrev.c
Kevin> and gdb/dwarf2/cooked-indexer.c.
I have some questions about this change.
How many symbols does it add, and what performance impact does it have?
I tend to think the indexer is fast primarily because it skips DIEs, but
IIUC this will have it read many more.
Do these declaration symbols end up in .debug_names and .gdb_index? I
suspect they should not. (Particularly for .debug_names which
specifically excludes them in the text of the standard.)
Does "break" on such a symbol result in many more CU expansions? If so
then I think this is a problem, because a declaration by its nature is
not useful for breakpoints.
What does "print malloc" say with this patch in place?
thanks,
Tom
next prev parent reply other threads:[~2025-09-05 15:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-03 19:45 Kevin Buettner
2025-08-12 0:23 ` Kevin Buettner
2025-08-12 14:48 ` Simon Marchi
2025-08-29 18:30 ` Andrew Burgess
2025-09-05 15:24 ` Andrew Burgess
2025-09-05 15:38 ` Tom Tromey [this message]
2025-09-05 16:20 ` Simon Marchi
2025-09-10 0:40 ` Tom Tromey
2025-09-13 0:55 ` Kevin Buettner
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=875xdwsye2.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=kevinb@redhat.com \
/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: link
Be 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