Re: [Valgrind-users] unable to locate exact location of leak.

[David E. <da...@2g...>]

On Fri, 2006-10-20 at 06:53 -0700, Srivatsan Ramanujam wrote:
> Hi People,
> 
> I have been trying to run valgrind to detect leaks in
> my backend C++ algorithm.
> 
> The algorithm is created as a shared library object, I
> have writtten a small program testAlgo.cpp as an
> interface to this algorithm and I am running valgring
> on this program using 
> 
> make runval <filename>
> 
> where runval is defined as 
> 
> --------------------------------------
> runval:	testAlgo
> 	$(ENVIRON) $(MOREPATHS) valgrind --leak-check=full
> --error-limit=no --show-reachable=no ./testAlgo $(FN)
> --------------------------------------
>
> [snip]

The source to ABCParser::parseString() would be useful to get a better
idea of what is going on.

Maybe you should try to add the below defines to the CXXFLAGS for the
whole project, and rebuild everything. That should add validations to
certain STL operations and maybe that will pinpoint the error better
than valgrind:
 
 -D_GLIBCXX_DEBUG -D_GLIBCXX_DEBUG_PEDANTIC


\David