public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dhoyer at netapp dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/81932] Template arguments of type unsigned generate incorrect debugging information
Date: Thu, 11 Mar 2021 19:17:01 +0000 [thread overview]
Message-ID: <bug-81932-4-cF2SNiPS8E@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-81932-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81932
David Hoyer <dhoyer at netapp dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |dhoyer at netapp dot com
--- Comment #31 from David Hoyer <dhoyer at netapp dot com> ---
(In reply to robert@ocallahan.org from comment #30)
> (In reply to Xi Ruoyao from comment #27)
> > Yes. Could GDB search the symbol with linkage name?
>
> This might work for function names but if you're trying to look up a type
> name (e.g. for a cast expression) this doesn't work because types don't have
> linkage names. We can often find a mangled name for a type as part of a
> function or global variable linkage name, but we can't guarantee that.
>
> Taking a user-provided type name and converting it into something we can
> look up in DWARF is already pretty hard due to C++ vagaries, but not knowing
> how the compiler canonicalizes these names makes it even harder, and it
> would simplify things if the compiler at least matches the demangler.
This issue has gotten stale and yet is still a problem for us using debian
buster. Is there any update?
next prev parent reply other threads:[~2021-03-11 19:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-81932-4@http.gcc.gnu.org/bugzilla/>
2020-04-29 12:28 ` robert at ocallahan dot org
2020-04-29 12:50 ` robert at ocallahan dot org
2021-03-11 19:17 ` dhoyer at netapp dot com [this message]
2021-03-11 19:37 ` psmith at gnu dot org
2021-03-11 19:42 ` dhoyer at netapp dot com
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-81932-4-cF2SNiPS8E@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.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).