|
From: David N. <dav...@ho...> - 2004-02-14 12:44:24
|
Hi, I've just installed valgrind 2.0.0 and am having problems getting it to = work. I've complied the source on my LFS 5 system, done the make & make = install. And now whatever I try to do I get the error message = "/usr/bin/valgrind: '<progname>' not found in $PATH, aborting." (where = <progname> is the program I try after valgrind).=20 This is for everything even just "valgrind ls -l" gives this error. I'm = obviously doing/done something really stupid, but I can't figure out = what's wrong.=20 Can anyone point me in the right direction? Thanks, David |
|
From: Mathieu <mma...@ny...> - 2004-02-14 21:23:18
|
valgrind --skin=memcheck ls -l I think their no default skin. HTH Mathieu David Nunn wrote: > Hi, > > I've just installed valgrind 2.0.0 and am having problems getting it to > work. I've complied the source on my LFS 5 system, done the make & make > install. And now whatever I try to do I get the error message > "/usr/bin/valgrind: '<progname>' not found in $PATH, aborting." (where > <progname> is the program I try after valgrind). > > This is for everything even just "valgrind ls -l" gives this error. I'm > obviously doing/done something really stupid, but I can't figure out > what's wrong. > > Can anyone point me in the right direction? > > Thanks, > > David |
|
From: Nicholas N. <nj...@ca...> - 2004-02-14 22:32:03
|
On Sat, 14 Feb 2004, Mathieu wrote: > > I've just installed valgrind 2.0.0 and am having problems getting it to > > work. I've complied the source on my LFS 5 system, done the make & make > > install. And now whatever I try to do I get the error message > > "/usr/bin/valgrind: '<progname>' not found in $PATH, aborting." (where > > <progname> is the program I try after valgrind). > > > > This is for everything even just "valgrind ls -l" gives this error. I'm > > obviously doing/done something really stupid, but I can't figure out > > what's wrong. > > > > valgrind --skin=memcheck ls -l > > I think their no default skin. Not quite; v2.0.0 has Memcheck as the default, as does 2.1.0; the CVS HEAD doesn't have a default, though. As for why you're getting that error, no idea. Can you try fiddling with the 'which' test in coregrind/valgrind (the startup script) to work out what's going wrong? N |