Thanks Tom, You just confirmed what I have been researching.. Apparently this program grabs a few tidbits from the command line to make it's config file name and seems to grab the execution path for where to look for it. Looks like I have a bit of work to do before I can run Valgrind on it.
Thanks again Mike On Wed, Mar 26, 2014 at 3:44 PM, Tom Hughes <t...@compton.nu> wrote: > On 26/03/14 21:08, Mike Finneran wrote: > > I'm new to Valgrind, but I've used Valgrind to debug new/delete problems >> of a few small C++ programs(a few thousand lines of code), but now I'm >> trying to debug a larger one (60K+ lines of code) and I'm getting an >> apparently unusual error message. >> >> When I give the command: >> GSlice=allways-malloc G_DEBUG=gc-friendly valgrind -v --tool=memcheck >> --leak-check=full --num-callers=40 --log-file=valgrind.log ./l2a >> ../bdti/DSP_w_vec.bc >> >> I get the output: >> Filename: /usr/bin/valgrdefault.conf >> FATAL ERROR: config::parse(): File open failed >> >> I can't seem to find any reference to valgrdefault.conf on the Net of in >> the Docs. >> > > That's not a message from valgrind - it will be a message from your > program. > > At a guess it is doing something "clever" by taking argv[0] something in > /proc that points to the path of the current executable and and trying to > modify it to point to a config file and getting confused by the fact that > it is the path to valgrind rather than it's path. > > Tom > > -- > Tom Hughes (t...@compton.nu) > http://compton.nu/ >
------------------------------------------------------------------------------
_______________________________________________ Valgrind-users mailing list Valgrind-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-users
