public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tromey at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/49130] New: discrepancies between DW_AT_name and demangler
Date: Mon, 23 May 2011 21:34:00 -0000	[thread overview]
Message-ID: <bug-49130-4@http.gcc.gnu.org/bugzilla/> (raw)

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: unassigned@gcc.gnu.org
        ReportedBy: tromey@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


             reply	other threads:[~2011-05-23 21:11 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-23 21:34 tromey at gcc dot gnu.org [this message]
2011-05-24 10:54 ` [Bug debug/49130] " rguenth at gcc dot gnu.org
2011-05-27 13:59 ` jan.kratochvil at redhat dot com
2011-05-27 17:03 ` tromey at gcc dot gnu.org
2011-05-27 17:14 ` tromey at gcc dot gnu.org
2011-05-27 17:39 ` dodji at seketeli dot org
2011-05-30  8:46 ` jan.kratochvil at redhat dot com
2011-05-31 11:57 ` dodji at seketeli dot org
2011-06-07 11:13 ` dodji at gcc dot gnu.org
2011-06-07 22:22 ` dodji at seketeli dot org
2011-06-07 22:27 ` dodji at gcc dot gnu.org
2011-07-08 12:34 ` jan.kratochvil at redhat dot com
2023-01-12 18:53 ` dblaikie at gmail 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-49130-4@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).