[PATCH] coverage : Add support to run coverage in supported bsp without extra options

[Vijay Kumar Banerjee]

I'm running rtems-test with the following command

$HOME/development/rtems/test/rtems-tools/tester/rtems-test \
--rtems-tools=$HOME/development/rtems/5 --log=coverage_analysis.log \
--no-clean --coverage=score --rtems-bsp=leon3-qemu-cov \
/home/lunatic/development/rtems/kernel/leon3/sparc-rtems5/c/leon3/testsuites/samples

I'm getting this error

---------
error: coverage: covoar failure:: -11
-------
On 19 June 2018 at 09:06, Vijay Kumar Banerjee <vijaykumar9597 at gmail.com>
wrote:

>
>
> On Tue, 19 Jun 2018, 08:54 Chris Johns, <chrisj at rtems.org> wrote:
>
>> On 19/06/2018 13:16, Vijay Kumar Banerjee wrote:
>> >     I would like to get my 22 patches pushed to master before moving on
>> this topic.
>> >     This is the report I generate:
>> >
>> >     https://ftp.rtems.org/pub/rtems/people/chrisj/coverage/
>> leon3/leon3-qemu-report.html
>> >
>> >     How does this look?
>> >
>> > The report looks good.
>> > This report is from two subsystems score and rtems
>> > that are mentioned in the symbols ini file.
>>
>> Excellent, I will push the patches. I have just run all the samples and
>> updated
>> the report.
>>
> Awesome! report looks good.
>
>>
>> I get the size warning ...
>>
> Yes, I'm getting these warnings as well.
>
>>
>> INFO: DesiredSymbols::createCoverageMap - Attempt to create unified
>> coverage
>> maps for _Workspace_Allocate_or_fatal_error with different sizes
>> (/opt/work/chris/rtems/kernel/bsps/leon3/sparc-rtems5/c/
>> leon3/testsuites/samples/capture.exe/80!=
>> /opt/work/chris/rtems/kernel/bsps/leon3/sparc-rtems5/c/
>> leon3/testsuites/samples/base_sp.exe/60)
>>
>> My version of covoar has the DWARF function details from for a CU for an
>> executable so it will be interesting to see what this shows. I will take
>> a look
>> at some point.
>>
> I was hoping that these warnings would go away after your covoar patches
>
>>
>> Also the execute wrapper needs to catch stderr and redirect that to the
>> log. I
>> will take a look at that.
>>
>> Chris
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/devel/attachments/20180623/e8097a46/attachment-0002.html>