From: Tom Tromey <tromey@redhat.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org, Petr Machata <pmachata@redhat.com>
Subject: Re: DWARF sanity checking [Re: [patch] Fix empty PC range psymtab<->symtab discrepancy]
Date: Tue, 15 Mar 2011 16:26:00 -0000 [thread overview]
Message-ID: <m3bp1c8ilw.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20110315160010.GA19529@host1.jankratochvil.net> (Jan Kratochvil's message of "Tue, 15 Mar 2011 17:00:10 +0100")
>>>>> "Jan" == Jan Kratochvil <jan.kratochvil@redhat.com> writes:
Tom> Thanks for putting this info into the complaint.
Tom> One of my minor wish-list items is that we would do this for all DWARF
Tom> complaints.
Jan> While not a GNU project this functionality overlaps with the
Jan> pmachata/dwarflint branch of elfutils which should be more complete
Jan> as the checks are not just a side-effect. Unaware how easy would
Jan> be to port it for non-ELF DWARF and whether the elfutils GPL
Jan> exception is good enough for FSF.
Yeah, I don't think gdb's DWARF reader will or should try to do what
dwarflint does. But I also doubt we'll ever remove the complaints from
dwarf2read.c; and of course gdb may emit complaints that dwarflint will
not (e.g., for valid but odd stuff not handled by gdb). And, given that
we will probably always have complaint calls, I think they should
provide enough information to actually find the problem DIE.
Tom
prev parent reply other threads:[~2011-03-15 16:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-14 18:16 [patch] Fix empty PC range psymtab<->symtab discrepancy Jan Kratochvil
2011-03-15 15:51 ` Tom Tromey
2011-03-15 16:16 ` DWARF sanity checking [Re: [patch] Fix empty PC range psymtab<->symtab discrepancy] Jan Kratochvil
2011-03-15 16:26 ` 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=m3bp1c8ilw.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=pmachata@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