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

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

Crispin Flowerday <cr...@th...> schrieb am 22.04.03 13:05:20:
> 
> On Tue, 2003-04-22 at 11:55, Nicholas Nethercote wrote:
> > On Tue, 22 Apr 2003, Joerg Beyer wrote:
> > 
> > > ok, apache seems to close the filedescriptor - if I use
> > > --logsocket, then I could see the valgrind output.
> > 
> > That's a bit odd... Valgrind checks close() syscalls for exactly this
> > case.  Did you not get any message like this:
> > 
> >   Warning: client attempted to close Valgrind's logfile fd (x).
> >   Use --logfile-fd=<number> to select an alternative logfile fd.
> 
> I have a feeling that Apache will open it's error log file, then use
> dup2() to map stderr to that file. I get valgrind errors in my apache
> error log file when I run it, perhaps the check for valgrind's logfile
> should be in the dup2() system call as well?

yes, hidden under a large pile of other messages. Thanks for
pointing it out.

It now detects my errors that I have inserted with intention.

Please excuse - it was my mistake not to find the valdgrind messages.


    Joerg