Bug 393023 - callgrind_control risks using the wrong vgdb
Summary: callgrind_control risks using the wrong vgdb
Status: RESOLVED FIXED
Alias: None
Product: valgrind
Classification: Developer tools
Component: callgrind (show other bugs)
Version: 3.13 SVN
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Josef Weidendorfer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-04-11 21:15 UTC by John Reiser
Modified: 2018-04-15 10:45 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description John Reiser 2018-04-11 21:15:24 UTC 
The perl script 'callgrind_control' sub-invokes 'vgdb' free in $PATH:
  open LIST, "vgdb $vgdbPrefixOption -l|";
  open RESULT, "vgdb $vgdbPrefixOption --pid=$pid $vgdbCommand|";
which might invoke a mismatching vgdb (stale version in abandoned directory, etc.)

It would be safer to look for vgdb first in the installation tree of valgrind tools, typically the same tree in which the running 'callgrind_control' resides.

[Low priority, but the problem has happened.]
Comment 1 Philippe Waroquiers 2018-04-15 10:45:34 UTC 
Fix committed as 532ed8a48b72231f424dd0b421cceb91d601389a

Thanks for the bug report