From: Roland McGrath <roland@redhat.com>
To: Project Archer <archer@sourceware.org>
Subject: dwarflint
Date: Fri, 10 Sep 2010 07:39:00 -0000 [thread overview]
Message-ID: <20100910073927.682CE405D5@magilla.sf.frob.com> (raw)
Petr has been working on dwarflint again, and he's just posted a big
update to the elfutils wiki. Please take a look at
https://fedorahosted.org/elfutils/wiki/DwarfLint
and the TODO file and SuspiciousDebuginfoCases page linked from there.
Please follow up on elfutils-devel@lists.fedorahosted.org about details.
There is now a pretty thorough description of the checks dwarflint does.
The TODO lists all the others we've thought of or had suggested, unless we
dropped some on the floor. If you have any more suggestions for checks,
please post them to elfutils-devel and we'll get them onto the TODO list.
Especially, if you have come across bad data emitted by GCC that is not
listed on SuspiciousDebuginfoCases, then let us know--and no less so if
GCC has already been fixed. We certainly want to add regression tests
for all the known cases of bad DWARF emitted. We're also hoping to
track the details of which GCC versions had each bug and when it got
fixed, for the eventual "quirks table" feature that will allow filtering
out known issues from analysis of old data from historical builds.
Certainly feel free to do your own editting on the elfutils wiki if you
have stuff to add. But please be vocal on elfutils-devel too.
Thanks,
Roland
reply other threads:[~2010-09-10 7:39 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20100910073927.682CE405D5@magilla.sf.frob.com \
--to=roland@redhat.com \
--cc=archer@sourceware.org \
/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).