From: Tom Tromey <tromey@redhat.com>
To: Sterling Augustine <saugustine@google.com>
Cc: gdb@sourceware.org
Subject: Re: Differences between Gold-produced gdb-index and GDB-produced gdb-index
Date: Wed, 05 Oct 2011 20:29:00 -0000 [thread overview]
Message-ID: <m38vozi3mp.fsf@fleche.redhat.com> (raw)
In-Reply-To: <CAEG7qUykGLNyTpkHv9UvaX4jQWH1W2paj9qtWO6iR+Xy1MOaNA@mail.gmail.com> (Sterling Augustine's message of "Wed, 5 Oct 2011 12:07:24 -0700")
>>>>> "Sterling" == Sterling Augustine <saugustine@google.com> writes:
Sterling> [Resend now that tromey is back.]
I just sent a reply a few minutes ago :-)
Maybe I was confused then though.
Sterling> A_A
Sterling> foo::B::B_B
Sterling> That seems wrong to me. Which is right? FWIW, Gold includes the enum
Sterling> name in both cases.
I think the right answer is A_A and foo::B_B.
I am not completely positive.
I think what you'd have to do is dig into gdb to see what is the right
answer for expression parsing, symbol lookup, etc; then make sure that
gdb actually uses this in its symbol tables. The index has to reflect
whatever gdb decides; but this does not necessarily imply that gdb is
presently correct.
Tom
prev parent reply other threads:[~2011-10-05 20:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-05 19:07 Sterling Augustine
2011-10-05 20:29 ` Tom Tromey [this message]
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=m38vozi3mp.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb@sourceware.org \
--cc=saugustine@google.com \
/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).