http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49130
Summary: discrepancies between DW_AT_name and demangler
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: debug
AssignedTo: unassig...@gcc.gnu.org
ReportedBy: tro...@gcc.gnu.org
>From the tail of this email:
http://sourceware.org/ml/gdb-patches/2011-05/msg00524.html
There are a number of places where DW_AT_name disagrees with the demangler:
Computed physname <WTF::FixedArray<double, 8u>::data()> does not match
demangled <WTF::FixedArray<double, 8ul>::data()> (from linkage
<_ZN3WTF10FixedArrayIdLm8EE4dataEv>)
- FYI its DW_TAG_class_type DW_AT_name is: FixedArray<double, 8u>
Computed physname <WTF::PtrHash<void const*>::hash(void*)> does not match
demangled <WTF::PtrHash<void const*>::hash(void const*)> (from linkage
<_ZN3WTF7PtrHashIPKvE4hashES2_>)
- const issue
Computed physname <WebCore::RangeBoundaryPoint::offset()> does not match
demangled <WebCore::RangeBoundaryPoint::offset() const> (from linkage
<_ZNK7WebCore18RangeBoundaryPoint6offsetEv>)
- maybe different const issue
(I didn't verify the const issues in the DWARF, it may be a gdb bug)
I think it would be best if DW_AT_name matched the demangler in all cases.
(I think it is arguable whether DW_AT_name should include the template
parameters; but we should at least discuss on the gdb list before considering
this, and anyway this would require a complete solution to PR 41736)
See also PR 33861
