From: Tom Tromey <tromey@redhat.com>
To: Cary Coutant <ccoutant@google.com>
Cc: Dodji Seketeli <dodji@redhat.com>,
"GDB\/Archer list" <archer@sourceware.org>
Subject: Re: [RFC] Proposal for a new DWARF name index section
Date: Fri, 11 Dec 2009 23:56:00 -0000 [thread overview]
Message-ID: <m3fx7hvze5.fsf@fleche.redhat.com> (raw)
In-Reply-To: <c17be2b30911171545k302106bfuf526378d52e0a324@mail.gmail.com> (Cary Coutant's message of "Tue, 17 Nov 2009 15:45:59 -0800")
>>>>> "Cary" == Cary Coutant <ccoutant@google.com> writes:
Cary> Now how will gdb know whether or not the pubnames index actually has
Cary> all of this extra info? A suggestion to have gdb look at the producer
Cary> string was shot down as ugly, but compare that to the alternative of
Cary> using a non-standard index. You could instead tie it to the switch to
Cary> DWARF-4 and just check the section version number in the compilation
Cary> unit header (the version number for .debug_pubnames isn't scheduled to
Cary> change with DWARF-4, unfortunately). Another alternative is just to
Cary> have gdb use the pubnames index if it's present, and any name that
Cary> isn't in the index simply won't be found without qualification.
It occurred to me today that we could define a GNU-local attribute that
GCC (and whatever DWARF-rewriting tool we come up with to generate the
indices post-facto) can put into the CU DIE.
What do you think of that?
Tom
next prev parent reply other threads:[~2009-12-11 23:56 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-10 9:04 Dodji Seketeli
2009-08-10 14:38 ` Jan Kratochvil
2009-08-10 17:36 ` Tom Tromey
2009-08-10 18:21 ` Jan Kratochvil
2009-08-11 7:55 ` Dodji Seketeli
2009-08-11 17:45 ` Jan Kratochvil
2009-08-11 22:43 ` Tom Tromey
2009-08-12 19:20 ` Jan Kratochvil
2009-08-11 22:29 ` Tom Tromey
2009-08-20 17:31 ` Dodji Seketeli
2009-11-17 23:46 ` Cary Coutant
2009-11-20 17:25 ` Tom Tromey
2009-11-22 4:39 ` Daniel Jacobowitz
2009-11-23 19:51 ` Tom Tromey
2009-12-01 19:14 ` Tom Tromey
2009-12-02 5:17 ` Daniel Jacobowitz
2009-12-02 17:07 ` Tom Tromey
2009-12-02 17:35 ` Daniel Jacobowitz
2009-12-02 19:23 ` Tom Tromey
2009-12-02 19:39 ` Daniel Jacobowitz
2009-12-03 1:46 ` Paul Pluzhnikov
2009-12-04 23:13 ` Tom Tromey
2009-12-06 3:41 ` Tom Tromey
2009-12-07 21:32 ` Tom Tromey
2009-12-02 16:11 ` Dodji Seketeli
2009-12-02 17:29 ` Tom Tromey
2009-12-11 23:56 ` Tom Tromey [this message]
2009-12-12 0:06 ` Daniel Jacobowitz
2009-12-12 0:13 ` Cary Coutant
2009-12-13 3:48 ` Dodji Seketeli
2009-12-14 15:32 ` Dodji Seketeli
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=m3fx7hvze5.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=archer@sourceware.org \
--cc=ccoutant@google.com \
--cc=dodji@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).