dennyk

Forum Replies Created

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • in reply to: Setting location of coverage reports through command line #20027
    dennyk
    Participant

    Hi,

    Before trying that..

    Now I am suspecting that visualGdb fails to find the debug files from HW target..

    When copying debug files from HW target, where are they expected to be? In my case I find them manually in directory specified in ‘Project properties -> Configuration Properties -> instrumentation -> Coverage Report Directory’\<Project_Name>\<Project_Config>, which I never changed, seems to be the default and seems to work when I run everything from the GUI. The one that I changed is under ‘VisualGdb Project Properties -> Code Coverage -> Directory to store coverage reports’, which is set to somewhere in my PC.

    So what is the difference for the path set under project properties and the path set under visualGdb properties?

    Is it possible that when test is run from GUI, it knows the gcda files are in the path set under project properties and not when it’s run from cmd line? If that is the case, what path am I supposed to set for the one under project properties?

    in reply to: Setting location of coverage reports through command line #20025
    dennyk
    Participant

    Hi,

    I checked the registry editor to make sure, “KeepRawCoverageReports” under HKEY_CURRENT_USER\SOFTWARE\Sysprogs\VisualGDB\Settings\Common\Profiling is 1. So I should be good.

    And I remove all old coverage reports from my build dir, which is where I set it to be. and Run “<path_to_visualgdb>\VisualGDB.exe /runtests <path_to_container>\adrv9010gdbgtest.vgdbtestcontainer /output:testOutput.xml” from command line. And when I checked my build_dir again, there is the scovreport file, and the directory with a timestamp. But that directory only contains an empty job.txt file and nothing else.

    So what am I missing here? I believe there should be gcda gcno and gcov files in that directory with a time stamp.. Please help..

    in reply to: Setting location of coverage reports through command line #20016
    dennyk
    Participant

    Hi,

    I’m running it on the same machine where if i run my test from visual studio’s test explorer, i see the raw files. So i believe i wouldn’t need to export those settings. So is there any other explanation why the raw files are not kept if i run it through command line?

    in reply to: Setting location of coverage reports through command line #20005
    dennyk
    Participant

    Hi,

    Thanks for the help, with that version, I can see the scovreport file, but I also set the option for “Keep raw coverage reports”. I can see the directory that normally contains the raw coverage reports if I run my test from visual studio’s test explorer, but it is empty, the job.txt is there, but also empty. It’s those raw coverage files that I really need, especially the gcda files as I do the processing on my own. Is there a way that can be fixed? Or is there another version that also has that fixed? Or is there a command line option I need to use? Please help…

    • This reply was modified 6 years, 10 months ago by dennyk.
Viewing 4 posts - 1 through 4 (of 4 total)