It's A) :
The build of the executable succeed.
Running the executable with drmemory ( as a jenkins build step with my fork https://github.com/asmodehn/drmemory-plugin and https://github.com/asmodehn/drmemory-api to be able to run with spaces in logdir path ) gives me :
Dr Memory Plugin version 0.1.1
Executing C:\Program Files (x86)\Jenkins\workspace\Project Debug\bin\vs2010\Debug\Project.V2.DB.test_d.exe -xml
Setting log path to C:\Program Files (x86)\Jenkins\workspace\Project Debug\bin\vs2010\Debug\9
Recieved Unable to execute drmemory.exe -logdir "C:\Program Files (x86)\Jenkins\workspace\Project Debug\bin\vs2010\Debug\9" -batch -quiet – "C:\Program Files (x86)\Jenkins\workspace\Project Debug\bin\vs2010\Debug\Project.V2.DB.test_d.exe" -xml:
[Project Debug] $ cmd /c call C:\Windows\TEMP\hudson2236794367891390495.bat
And then the graph is not displayed.
However, the run actually succeeds ( and the logdir is created and filled up with drmemory analysis files ).
I am guessing that there is an incorrect/unexpected error detection upon running the .exe with drmemory:
- my exe returns output on the console -> might be detected as exception by the plugin.
- my exe exit with a non-null exit status code ( this is what I expected as it is an incomplete unit test ).
I am not sure what would be the best fix here, given all the different possible use-cases out there. But I think some advanced options might be the way to go...
Thanks for the help !