public inbox for archer@sourceware.org
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Roland McGrath <roland@redhat.com>
Cc: Daniel Jacobowitz <drow@false.org>, archer@sourceware.org
Subject: Re: Initial psymtab replacement results
Date: Wed, 16 Dec 2009 18:20:00 -0000	[thread overview]
Message-ID: <m31viulr0w.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20091216030118.A676A1D7@magilla.sf.frob.com> (Roland McGrath's message of "Tue, 15 Dec 2009 19:01:18 -0800 (PST)")

>>>>> "Roland" == Roland McGrath <roland@redhat.com> writes:

Roland> (Perhaps there is something easy and kosher to do that GDB could
Roland> use as an indicator of a .debug_aranges worth using.)

I don't think so, or at least, I couldn't think of anything.  Our
current branches, including F12, check for a known GCC bug, but
otherwise assume that if aranges exists, it is correct.

There's also an issue with knowing whether it is actually complete; I
didn't think of this until relatively recently:
    http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42288

Roland> With .debug_pub* it has always been my impression that the extraction
Roland> from the DIE tree is not fully generic.  That is, it at least assumes
Roland> some language-specific knowledge to construct foo::bar names and the
Roland> like.  I've never been entirely clear on if it's even entirely knowable
Roland> just from very simple language knowledge as opposed to encoding some
Roland> choices or extra knowledge the compiler had.

I think this question is related to Keith's work on avoiding
DW_AT_MIPS_linkage_name.  I think the current answer is that there are
some known missing DWARF features relating to C++.  However, Keith and
Dodji have worked on GNU extensions for at least some of these.

Tom

  reply	other threads:[~2009-12-16 18:20 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-10 21:54 Tom Tromey
2009-12-11 23:10 ` Tom Tromey
2009-12-11 23:59   ` Daniel Jacobowitz
2009-12-14 22:40     ` Tom Tromey
2009-12-14 23:09       ` Daniel Jacobowitz
2009-12-15 23:39         ` Tom Tromey
2009-12-16  3:01           ` Roland McGrath
2009-12-16 18:20             ` Tom Tromey [this message]
2009-12-16 18:57               ` Roland McGrath
2009-12-16 19:46                 ` Tom Tromey
2009-12-16 19:52                   ` Roland McGrath
2009-12-16 18:11           ` Daniel Jacobowitz
2009-12-16 19:31             ` Tom Tromey
2009-12-23 18:29           ` Tom Tromey
2009-12-23 18:35             ` Daniel Jacobowitz
2009-12-24 17:07             ` Tom Tromey
2010-01-06 23:05               ` Tom Tromey
2009-12-17 16:39         ` Paul Pluzhnikov
2009-12-17 16:53           ` Daniel Jacobowitz
2009-12-17 17:20             ` Paul Pluzhnikov
2009-12-17 18:16               ` Daniel Jacobowitz
2009-12-18 23:58                 ` Tom Tromey
2009-12-21 13:54                   ` Daniel Jacobowitz
2009-12-21 21:29                     ` Tom Tromey
2009-12-15  1:04       ` Roland McGrath
2009-12-15 18:36         ` Tom Tromey

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=m31viulr0w.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=archer@sourceware.org \
    --cc=drow@false.org \
    --cc=roland@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).