https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94845
--- Comment #10 from Tom Tromey ---
See also bug #49130 and bug #49537, which we filed when
gdb hit these same problems.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94845
--- Comment #9 from robert at ocallahan dot org
---
That makes sense ... well, except implementing a full C++ parser and
reserializer is horrific.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94845
--- Comment #8 from Tom Tromey ---
(In reply to rob...@ocallahan.org from comment #7)
> So gdb reads DW_AT_name "func", parses it, reserializes it to
> "func", and uses that?
Yeah. (Actually it's even worse than that, because at least one
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94845
--- Comment #7 from robert at ocallahan dot org
---
So gdb reads DW_AT_name "func", parses it, reserializes it to
"func", and uses that?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94845
Tom Tromey changed:
What|Removed |Added
CC||tromey at gcc dot gnu.org
--- Comment #6
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94845
--- Comment #5 from robert at ocallahan dot org
---
We do our best to consume what g++ produces, but in the situation of comment #1
that is difficult. Whether or not it's "correct DWARF" is really irrelevant;
not matching the demangler causes
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94845
--- Comment #4 from Andrew Pinski ---
See also PR 81932 where we talked about 2 and 2u
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94845
--- Comment #3 from Andrew Pinski ---
But that is just best practices, that does not mean an consumer of the dwarf
does not need to consume slightly different but still correct dwarf code.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94845
--- Comment #2 from Andrew Pinski ---
Hmm from http://wiki.dwarfstd.org/index.php?title=Best_Practices
For template instantiations, the DW_AT_name attribute should contain both the
source language name of the object and the template parameters
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94845
--- Comment #1 from robert at ocallahan dot org
---
One case where this causes problems is implementing a debugger where you want
to be able to evaluate expressions containing type names. Type names containing
template type parameters that are
10 matches
Mail list logo
