On 03/04/2018 02:10, Cillian O'Donnell wrote:
> Sure if you want to crack at it.
>
> If you pull the ini-update branch again, I've included the other files you'll
> need.
>
> Now if you try and run rtems-test with coverage you will get
>
> cpod@cpod ~ $ $HOME/development/rtems/test/rtems-tools/
Sure if you want to crack at it.
If you pull the ini-update branch again, I've included the other files
you'll need.
Now if you try and run rtems-test with coverage you will get
cpod@cpod ~ $ $HOME/development/rtems/test/rtems-tools/tester/rtems-test
--rtems-tools=$HOME/development/rtems/5 --log
Hello ,
I'm currently going through the coverage code , Can you please help me
understand what are the specific changes that are needed for the coverage
to be running again?
thanks
-- vijay
On 26 March 2018 at 09:30, Vijay Kumar Banerjee
wrote:
> 1. Yes , I plan to work on identifying the disc
