From: Dodji Seketeli <dodji@redhat.com>
To: Cary Coutant <ccoutant@google.com>
Cc: Tom Tromey <tromey@redhat.com>,
Project Archer <archer@sourceware.org>,
Sterling Augustine <saugustine@google.com>
Subject: Re: Generating gdb index at link time
Date: Sat, 06 Aug 2011 11:17:00 -0000 [thread overview]
Message-ID: <m3wrequ6vl.fsf@redhat.com> (raw)
In-Reply-To: <CAHACq4qhGTg7ShS-eoMHq1oDmoBj=GC=Bx06knVq-+XTUN4ohw@mail.gmail.com> (Cary Coutant's message of "Fri, 5 Aug 2011 13:30:35 -0700")
Hello,
Cary Coutant <ccoutant@google.com> writes:
>>> Tom> This problem was that .debug_pub* are explicitly for public names, but
>>> Tom> for GDB we wanted to see all names (so that "break staticfunction" works
>>> Tom> and "break typo" doesn't cause reading all CUs). This particular
>>> Tom> problem was resolved by you :) saying that we should just change GCC to
>>> Tom> emit all the names.
>>>
>>> Cary> No one has actually changed GCC to do that, yet, though -- right?
>>>
>>> I think either Dodji or I had a patch at one point. It may have been
>>> part of Dodji's patch to change .debug_pub* to also include all the
>>> extra info we thought we needed at the time.
>>>
>>> I'm not sure if it is still around.
>>
>> If you can find it, we'd definitely be interested in it.
I stored the iterations of that patch as attachments to
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41130 before dropping the
ball on this issue.
[...]
>>
>>> Cary> I think the biggest problem is an issue I've seen where the DIE for a
>>> Cary> class isn't properly nested inside the right context (even after
>>> Cary> following DW_AT_specification). There's an ugly workaround for this in
>>> Cary> gdb (by looking for a member subprogram with a linkage name, and
>>> Cary> extracting the class name from that), which I copied into gold. As
>>> Cary> part of this work, I'd like to fix that bug in GCC, and any others
>>> Cary> like it.
>>>
>>> Yeah. We've tried to file and/or fix problems like this as we've run
>>> across them. There are still some open bugs around naming.
>>>
I'd be interested in looking into these nesting bugs when I have some
free cycles. Please CC me on these.
Thanks.
--
Dodji
next prev parent reply other threads:[~2011-08-06 11:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAHACq4oHymXfBOqzJfyzQXNyW5PYkN6g65X6x1rMU+YmJybZmQ@mail.gmail.com>
[not found] ` <m3d3gkx8ar.fsf@fleche.redhat.com>
[not found] ` <CAHACq4ofyavZBt4y65OfYSoeW--HeEAT=sz86urLC0MXBB0hnA@mail.gmail.com>
[not found] ` <m3d3gjwuho.fsf@fleche.redhat.com>
[not found] ` <CAHACq4poC0QkGowdHkg0_Y1FRmyXTZZDeoBYrUf91nxz9SJtQw@mail.gmail.com>
2011-08-05 20:30 ` Cary Coutant
2011-08-06 11:17 ` Dodji Seketeli [this message]
2011-08-10 20:12 ` Daniel Jacobowitz
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=m3wrequ6vl.fsf@redhat.com \
--to=dodji@redhat.com \
--cc=archer@sourceware.org \
--cc=ccoutant@google.com \
--cc=saugustine@google.com \
--cc=tromey@redhat.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).