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.
Thank
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.
>
>
Hi
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
