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

[Nicholas N. <nj...@ca...>]

On Tue, 22 Apr 2003, Joerg Beyer wrote:

> I have a complicated setup where valgrind is not finding errors.
> In my setup I have a apache 1.3 with a c++ module, so it
> is mixed C/C++ code. Even at the very first call to initialize
> valgrind is not detecting a new[100]/delete (not delete [] !)
> pair of calls as error.
>
> Apache introduces some difficulties for valgrind:
> - it is mixed C/C++ code
> - all kinds of signal are catched by a signal handler
> - all kinds of libraries are linked to the module, like xalan, xerces
> - it is a large application with a memory footprint of ~ 20 MB.

None of these should pose a problem.

What I think is the most likely cause: does your program spawn
sub-processes, or is it started from a shell or Perl script?  By default,
Valgrind only traces the top process;  if the program starts with a
script, Valgrind will trace your shell interpreter or the Perl
interpreter.  Use --trace-children=yes to trace all processes.

N