Re: Re: Re: Re: [Valgrind-users] valgrind not finding errors in apache c++ module

[Joerg B. <j....@we...>]

Nicholas Nethercote <nj...@ca...> schrieb am 22.04.03 11:18:30:
> 
> On Tue, 22 Apr 2003, Joerg Beyer wrote:
> 
> > > If so... your program isn't statically linked?  Valgrind doesn't work with
> > > statically linked apps.  Is Valgrind starting up -- ie. you're getting the
> >
> > ok, that may be the part I was missing. some parts are linked as archive
> > (e.g. python.a). This is not possible? If so, excuse for missing this part
> > of the documentation.
> 
> No, that should be fine.  It's only a problem if the whole program is
> statically linked, in which case Valgrind won't even start up.
> 
> > > Have you tried Valgrind with other programs, eg. small test ones that have
> > > deliberate errors in them?  What version of Valgrind are you using?
> >
> > yes, but other, smaller programms work as expected and detect the errors.
> > valgrinds version is 1.9.5
> 
> Hmm, very strange.  Are you certain that the obvious error you inserted is
> being executed?  Maybe #include memcheck.h and insert a call to

yes, I have picked a place in the source that is executed on inititalization
of the apache module.  I even put debug messages before and after that
place (both appeared in the logfile).

> VALGRIND_DO_LEAK_CHECK and see if that runs, to make sure that (a) the
> code is being executed and (b) that Valgrind is seeing the code.  I can't
> think why Valgrind wouldn't be seeing the code, but this behaviour is
> weird.
> 
> Apart from that, I'm all out of ideas for the moment, sorry.
>

thanks for the guesses. I try to strip the complex code 
simpler code and post again if I am able to reduce it so 
something simple enough.


    Joerg