From: Tom Tromey <tom@tromey.com>
To: Bruno Larsen via Gdb-patches <gdb-patches@sourceware.org>
Cc: Bruno Larsen <blarsen@redhat.com>
Subject: Re: [PATCH v2 2/2] gdb/c++: Improve error messages in overload resolution
Date: Wed, 09 Nov 2022 10:47:28 -0700 [thread overview]
Message-ID: <87zgd010lr.fsf@tromey.com> (raw)
In-Reply-To: <20221104154744.418906-3-blarsen@redhat.com> (Bruno Larsen via Gdb-patches's message of "Fri, 4 Nov 2022 16:47:45 +0100")
>>>>> "Bruno" == Bruno Larsen via Gdb-patches <gdb-patches@sourceware.org> writes:
Bruno> When resolving overloaded functions, GDB relies on knowing relationships
Bruno> between types, i.e. if a type inherits from another. However, some
Bruno> compilers may not add complete information for given types as a way to
Bruno> reduce unnecessary debug information. In these cases, GDB would just say
Bruno> that it couldn't resolve the method or function, with no extra
Bruno> information.
Thanks for the patch. This looks good to me.
I wonder if this could be the problem underlying
https://sourceware.org/bugzilla/show_bug.cgi?id=28901
Tom
next prev parent reply other threads:[~2022-11-09 17:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-04 15:47 [PATCH v2 0/2] Improve error messages with incomplete variables Bruno Larsen
2022-11-04 15:47 ` [PATCH v2 1/2] gdb/testsuite: allowed for function_range to deal with mangled functions Bruno Larsen
2022-11-09 17:15 ` Tom Tromey
2022-11-10 11:41 ` Bruno Larsen
2022-11-10 13:44 ` Tom Tromey
2022-11-10 13:52 ` Bruno Larsen
2022-11-04 15:47 ` [PATCH v2 2/2] gdb/c++: Improve error messages in overload resolution Bruno Larsen
2022-11-09 17:47 ` Tom Tromey [this message]
2022-11-10 15:19 ` Simon Marchi
2022-11-10 15:29 ` Bruno Larsen
2022-11-10 15:45 ` Simon Marchi
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=87zgd010lr.fsf@tromey.com \
--to=tom@tromey.com \
--cc=blarsen@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).