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

Vijay Kumar Banerjee vijaykumar9597 at gmail.com
Sun May 13 15:32:34 UTC 2018


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

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/883e6506/attachment.html>


More information about the devel mailing list