From: Tom Tromey <tom@tromey.com>
To: Andrew Burgess <aburgess@redhat.com>
Cc: Tom Tromey <tom@tromey.com>, gdb-patches@sourceware.org
Subject: Re: [PATCHv3] gdb: remove attempted type de-duplication when building gdb-index
Date: Wed, 22 Oct 2025 11:21:16 -0600 [thread overview]
Message-ID: <874irqlunn.fsf@tromey.com> (raw)
In-Reply-To: <87ldl3c4h4.fsf@redhat.com> (Andrew Burgess's message of "Wed, 22 Oct 2025 16:59:19 +0100")
>> This also seems like something that could be fixed. For instance
>> completion could be done from the index as first pass.
Andrew> To be clear, this isn't just a completion issue. The example in PR
Andrew> gold/15646 is for 'break namespace_foo::misspelled', where this is also
Andrew> going to trigger expansion of many CUs.
Andrew> But maybe there's information that we could track better that would
Andrew> allow us to only expand a single CU in some cases?
For completion I had some thoughts, namely that the only time we need to
expand a CU for completion is when completing a C++ function, because I
think that's the only case where an index entry and a full symbol should
have different names.
For the "break prefix::fn" case, maybe if linespec sees that "prefix" is
a namespace it could stop the outer search.
It might still be an issue if "prefix" is a class since I think (1)
linespec may try to set breakpoints in superclass methods (not sure) and
(2) different CUs may have different views on a class, like different
template method instantiations. However at least (2) is a case of
getting what you asked for.
Tom
next prev parent reply other threads:[~2025-10-22 17:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-02 9:36 [PATCH] " Andrew Burgess
2025-10-16 18:11 ` [PATCHv2] " Andrew Burgess
2025-10-21 13:45 ` [PATCHv3] " Andrew Burgess
2025-10-22 15:17 ` Tom Tromey
2025-10-22 15:59 ` Andrew Burgess
2025-10-22 16:13 ` Andrew Burgess
2025-10-22 17:21 ` Tom Tromey
2025-11-04 14:23 ` Andrew Burgess
2025-10-22 17:21 ` Tom Tromey [this message]
2025-11-13 16:32 ` Andrew Burgess
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=874irqlunn.fsf@tromey.com \
--to=tom@tromey.com \
--cc=aburgess@redhat.com \
--cc=gdb-patches@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: 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