Does it work without --coverage flag?
On Tue, May 30, 2017 at 5:23 PM, Cillian O'Donnell <cpodonne...@gmail.com> wrote: > Ah nevermind.. just realised its already printing them out. > > On 30 May 2017 9:50 pm, "Cillian O'Donnell" <cpodonne...@gmail.com> wrote: >> >> Hi Tanu, >> >> Thanks for the help, I had been grepping through the files and >> backtracking through the definitions. I was just wondering was there a quick >> way to just print it out that I didn't know about. >> >> I also couldn't find the recipe for the bsp but the previous work I'm >> continuing on from worked for pc386 and leon2, the command I'm using is the >> standard command with an extra --coverage flag thats added in the work I'm >> continuing, it definitely worked in 2015. >> >> $HOME/development/rtems/test/rtems-tools/tester/rtems-test >> --rtems-bsp=pc386 \ >> --log=log_pc386 --coverage \ >> --rtems-tools=$HOME/development/rtems/4.12 \ >> $HOME/development/rtems/pc386/i386-rtems4.12/c/pc386/testsuites/ >> >> >> On 30 May 2017 at 20:34, Tanu Hari Dixit <tokencol...@gmail.com> wrote: >>> >>> Hi Cillian, >>> >>> I usually do a git grep -i "<string>" to find out where possibly a >>> macro or variable is used elsewhere in the code. Not the best way, but >>> works mostly. >>> Also %{qemu_cmd} has been defined here in the same file >>> >>> (https://devel.rtems.org/browser/rtems-tools/tester/rtems/testing/qemu.cfg#L60). >>> I also sometimes use winpdb to see what value a macro has but this is >>> a long process to step into each line. >>> I wanted to ask what command did you use exactly with rtems-test? I >>> couldn't find a recipe for qemu simulation for pc386 in >>> rtems-tools.git/tester/rtems/testing/bsps. >>> >>> Regards, >>> Tanu Hari Dixit. >>> >>> On Wed, May 31, 2017 at 12:42 AM, Cillian O'Donnell >>> <cpodonne...@gmail.com> wrote: >>> > Hi, >>> > >>> > I'm trying to run rtems-test for pc386 with the added --coverage tag >>> > for >>> > couverture-qemu. All tests default to dry-run because of errors in >>> > qemu.cfg >>> > >>> > error: qemu.cfg:81: execute failed: qemu-system-i386 -m 128 -boot b >>> > -hda >>> > >>> > /home/cpod/development/rtems/test/rtems-tools/tester/rtems/testing/coverage/rtems-boot.img >>> > -no-reboot -serial null -serial mon:stdio -nographic -append >>> > "--console=com1;boot;" -kernel >>> > >>> > /home/cpod/development/rtems/pc386/i386-rtems4.12/c/pc386/testsuites/samples/unlimited/unlimited.exe >>> > -exec-trace coverage/unlimited.exe.cov: exit-code:2 >>> > warning: switched to dry run due to errors >>> > >>> > The exit code I believe refers to 'no such file or directory'. In >>> > qemu.cfg >>> > the line is: >>> > >>> > %execute %{qemu_cmd} %{qemu_opts} -kernel %{test_executable} >>> > %{coverage_arg} >>> > >>> > It's a bit tricky to trace those macros back to different files and see >>> > what >>> > they have. Is there any way to just print those out when it runs so I >>> > can >>> > take a look at them. >>> > >>> > I tried %print %{qemu_cmd} and %echo %{qemu_cmd}. Is there any way to >>> > do >>> > this in a config file? >>> > >>> > Thanks, >>> > >>> > Cillian. >>> > >>> > _______________________________________________ >>> > devel mailing list >>> > devel@rtems.org >>> > http://lists.rtems.org/mailman/listinfo/devel >> >> > > _______________________________________________ > devel mailing list > devel@rtems.org > http://lists.rtems.org/mailman/listinfo/devel _______________________________________________ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel