coverage analysis failed
Gedare Bloom
gedare at rtems.org
Mon Aug 13 14:00:51 UTC 2012
A listing of exact commands used and the result (good, bad) would be
helpful.
On Mon, Aug 13, 2012 at 8:45 AM, Krzysztof Mięsowicz <
krzysztof.miesowicz at gmail.com> wrote:
> First I tried to invoke do_coverage with BSP declaring only but I saw that
> didn't run tests. Then I invoked do_coverage with -A option which means do
> all. I also tried it without updating, configuring and building rtems as it
> has been done earlier.
>
> I have just run pc386 with -c option (coverage on) for hello.exe and it
> seems to work properly. It generated log and hello.exe.cov file also.
>
> 2012/8/13 Joel Sherrill <Joel.Sherrill at oarcorp.com>
>
>> How did you invoke the do_coverage script?
>>
>> Which any did it report using?
>>
>> Can you run the pc386 script on hello with the coverage option and see what happens?
>>
>> If it doesn't work on a simple case that is one thing.
>>
>>
>>
>> Krzysztof Mięsowicz <krzysztof.miesowicz at gmail.com> wrote:
>>
>>
>> Hi all,
>> I'm Krzysztof and I'm this year ESA SOCIS student. I'm working on RTEMS
>> coverage improvement. Actually I'm trying to prepare environment to run
>> coverage analysis on my laptop and I have some troubles with it. I had some
>> problems with was due to lack of qemu and path to qemu but this is solved.
>> I have run do_coverage script. It executed all tests but then I get a lot
>> of warnings such as
>> "WARNING: Unable to read coverage file unlimited.exe.cov" and error:
>> "ERROR: No information to analyze"
>> FAILED: covoar failed
>>
>> I'm very confused with it and hope anyone can help me :)
>>
>> Regards
>>
>> Krzysztof Miesowicz
>> krzysiekm13
>>
>>
>
> _______________________________________________
> rtems-devel mailing list
> rtems-devel at rtems.org
> http://www.rtems.org/mailman/listinfo/rtems-devel
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/devel/attachments/20120813/7e2045b5/attachment-0001.html>
More information about the devel
mailing list