Hi,
Thanks, we have linked your key to your profile. Regarding this error, please try enabling View->Other Windows->VisualGDB Diagnostics Console and starting a profiling session without debugging.
If it still doesn’t work, please take a note of the valgrind command line shown in the VisualGDB diagnostics console. It will show the path to the profiled program and some other arguments.
Please then try manually running valgrind with that program without any other options, e.g.
valgrind /tmp/my-program
Does valgrind work when launched manually? If yes, please post the exact command line you captured from VisualGDB Diagnostics Console and the exact command that worked manually.