[PATCH] covoar: fixing the extension mismatch in trace file

[Joel Sherrill]

On Sun, May 13, 2018, 11:33 AM Cillian O'Donnell <cpodonnell8 at gmail.com>
wrote:

>
>
> On 13 May 2018 at 16:32, Vijay Kumar Banerjee <vijaykumar9597 at gmail.com>
> wrote:
>
>> On 13 May 2018 at 19:00, Cillian O'Donnell <cpodonnell8 at gmail.com> wrote:
>>
>>> Is there supposed to be a message there?
>>>
>>> Anyway just to clear this up, try this for me.
>>>
>>> 1. Grab a new branch of
>>>
>>> https://github.com/cillianodonnell/rtems-tools/tree/tester-support
>>>
>>> which is the current master plus one patch with the tester support in
>>> progress.
>>>
>>> 2. Apply your patch to that and make no other changes.
>>>
>>> 3. Build covoar again.
>>>
>>> 3. Run the tester from the top of the build tree and tell me what you
>>> see.
>>>
>>> cpod at cpod ~/development/rtems/leon3 $
>>> $HOME/development/rtems/test/rtems-tools/tester/rtems-test
>>> --rtems-tools=$HOME/development/rtems/5 --log=coverage-analysis.log
>>> --rtems-bsp=leon3-qemu-cov --coverage
>>> $HOME/development/rtems/leon3/sparc-rtems5/c/leon3/testsuites/samples
>>>
>>>  Yes it's breaking .
>> when used with a single executable say unlimited.exe , it works but when
>> it's run with samples/ it returns the error :
>> executable build prefix does not match : sparc-rtems5
>>
>
> Yeah that's the one I'm seeing. Right so the difference is actually single
> or multiple executables. Interesting...
>

This may be a spot to add a message when verbose. Print the coverage file
associated with an executable.

But if it is just single vs multiple or 5 vs 4.11, run with 2 exes and use
gdb.



>> That's strange .
>> I think it has something to do with the parsing of the path from the ini
>> file.
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/devel/attachments/20180513/e8bab294/attachment-0002.html>