From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27633 invoked by alias); 10 Sep 2010 07:39:37 -0000 Mailing-List: contact archer-help@sourceware.org; run by ezmlm Sender: Precedence: bulk List-Post: List-Help: List-Subscribe: List-Id: Received: (qmail 27622 invoked by uid 22791); 10 Sep 2010 07:39:37 -0000 X-SWARE-Spam-Status: No, hits=-4.5 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_HI,SPF_HELO_PASS,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit From: Roland McGrath To: Project Archer Subject: dwarflint Message-Id: <20100910073927.682CE405D5@magilla.sf.frob.com> Date: Fri, 10 Sep 2010 07:39:00 -0000 X-SW-Source: 2010-q3/txt/msg00171.txt.bz2 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