This is the mail archive of the
elfutils-devel@sourceware.org
mailing list for the elfutils project.
Re: dwarflint aborts after "invalid" attribute?
- From: Josh Stone <jistone at redhat dot com>
- To: elfutils-devel at lists dot fedorahosted dot org
- Date: Mon, 18 Oct 2010 10:59:47 -0700
- Subject: Re: dwarflint aborts after "invalid" attribute?
On 10/18/2010 09:33 AM, Petr Machata wrote:
>> Thanks. Hmm, 280MB is too big for a test case. Does it fail on
>> anything of a more reasonable size, that I could add to the test suite?
Here's a small one, based on the "bad label PC" I reported before:
extern void exit (int);
static void foo (void)
{
x:
exit (0);
}
int main (void)
{
foo ();
return 0;
}
int bar __attribute__ ((__vector_size__ (4)));
It's the exact same test, just with the vector "bar" added.
> I added some elementary support for DW_AT_GNU*, it's on the dwarf
> branch. Singe DW_AT_GNU_vector is just a flag attribute, it might even
> be enough for your case.
Before, dwarflint would complain about DW_AT_GNU_vector and report
nothing else. With your fix, it's now fine with the vector, and it
correctly proceeds to report the bad PC range for the label. That 280MB
libxul now produces more output too, after 8 minutes of processing (vs.
the prior "instant" fail).
Thanks!
Josh