This is the mail archive of the
elfutils-devel@sourceware.org
mailing list for the elfutils project.
Re: dwarflint vs C++
- From: Petr Machata <pmachata at redhat dot com>
- To: elfutils-devel at lists dot fedorahosted dot org
- Date: Wed, 08 Jul 2009 22:09:25 +0200
- Subject: Re: dwarflint vs C++
08.07.2009 21:47, Roland McGrath wrote:
>> It checks all EXECINSTR | ALLOC sections for coverage.
>> If you point me to crt1.o with debuginfo, I can see if it works, and fix
>> it accordingly, but those that I can get my hands on are debuginfo-less.
>
> One of us is confused (or both!). I mentioned crt1.o precisely because it
That would be me, I didn't realize that it's .o.
> never has debuginfo. So it contributes to .text but not to any DWARF CU.
> (So it is the same as the general case of any statically linked libraries
> without debuginfo.) If you reported all EXECINSTR|ALLOC ranges not covered
> by any CU, then you'd already be reporting about the crt1.o regions.
Right. So why is it silent? Oh, right, because the coverage checking
code is turned off by #undef. I remember doing that, I think it was
something with me not being able to check NOP runs (which were often
uncovered IIRC). I don't think I wrote checking just in the CU
low_pc/high_pc range. I'll do that and see how it turns out.
PM