|
From: Brendan C. <bre...@xi...> - 2006-04-06 12:51:58
|
Hi, =20 I'm using valgrind for the first time. I'm using version 1.9.6 - installed on my employer's network. The tool is on my path - and I'm running the following line - where "xpower" is my debugged app's name : "valgrind --leak-check=3Dyes xpower". =20 I'm getting a message saying : "Skin error: The shared library 'vgskin_memcheck.so' for the chosen skin 'memcheck' could not be found at PATH1. Our installation of valgrind is actually not at PATH1 but rather is at PATH2. =20 Why is valgrind looking for the library at PATH1 ? =20 (I tried copying the tool's installation to PATH2 but I do not have write access to that part of our network.) =20 Thanks, =20 Brendan |
|
From: Tom H. <to...@co...> - 2006-04-06 13:14:12
|
In message <100AE4142881A8489779BF55E1832B3A028E676C@XIR-EXCHVS1.xlnx.xilinx.com> Brendan Cullen <bre...@xi...> wrote: > I'm using valgrind for the first time. I'm using version 1.9.6 - > installed on my employer's network. The tool is on my path - and I'm > running the following line - where "xpower" is my debugged app's name : > "valgrind --leak-check=yes xpower". Well my first suggestion would be to use a slightly less prehistoric version... > I'm getting a message saying : "Skin error: The shared library > 'vgskin_memcheck.so' for the chosen skin 'memcheck' could not be found > at PATH1. Our installation of valgrind is actually not at PATH1 but > rather is at PATH2. > > Why is valgrind looking for the library at PATH1 ? Because that is where valgrind was told it would be installed when it was built (basically what --prefix was set to at configure time with lib/valgrind added to it). Tom -- Tom Hughes (to...@co...) http://www.compton.nu/ |