Code changed in jenkins
User: Johannes Ohlemacher
Path:
src/main/java/org/jenkinsci/plugins/valgrind/ValgrindBuilder.java
src/main/resources/org/jenkinsci/plugins/valgrind/ValgrindBuilder/config.jelly
http://jenkins-ci.org/commit/valgrind-plugin/17bef8c049d3eb525dd66c6436d326964a2a7888
Log:
added support for arbitrary valgrind options (JENKINS-15139)
added support for program options (JENKINS-15138)

fixed with release 0.12

Is there any possibility to specify executable options within this plugin?

So far I can specify valgrind options, valgrind argument (the binary itself), the executable arguments - and how about executable options?

@Tomasz
what do you mean with "executable options"? the executable arguments are command line options passed to the executable under test.

@Johannes

Thanks for reply. I've got a C++ executable program that takes "-c" option which points configuration file path. The binary is executed in such way:

./service -c config_file.cfg

executable argument would be:

./service arg1

When I try to use executable arguments, the plugin executes following command:

valgrind [...] service "-c config_file.cfg"

and I'd like to run:

valgrind [...] service -c config_file.cfg

(without ")

@Tomasz
Thats just a bug, see JENKINS-16123. Its already fixed and will be part of the next release. Unfortunately you have to wait for the release until end of february, sorry