-
Improvement
-
Resolution: Unresolved
-
Major
-
None
Somethimes you do not want to build a program and execute lengthy valgrind/memcheck/hellgrind examination from within the same JENKINS jobs.
When workspace where a program is run under valgrind is different from the workspace where program was built the vagrant plugin will not be able to find sources.
In gdb this problem is solved using set-substitute-path. In valgring JENKINS plugin it is proposed that a source mappings are added.
Here is the link to gdb command documentation:
https://sourceware.org/gdb/onlinedocs/gdb/Source-Path.html#set%20substitute%2dpath
We stumbled across this, too. Would really be a great improvement, especially for a pipeline scenario as we have, with one jenkins job that builds the artifact and subsequent jobs that do testing.
@existence:
Any chance to get the pull request merged into the plugin source mainline? I'd volunteer for testing ...