|
From: Joerg B. <j....@we...> - 2003-04-22 07:24:34
|
Dear Listreaders,
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.
I inserted the obvious error, because valgrind is not
finding any kind of errors within the module and I cant
believe that :-)
I also introduced other obvius errors (like free'ing not malloc
memory - this is a pure C eror, no C++) without success.
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.
I am ware that this is very difficult task for valgrind. Is there anything
I could do to track down, why valgrind is not detecting errors?
Joerg
|
|
From: Nicholas N. <nj...@ca...> - 2003-04-22 07:47:48
|
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 |
|
From: Madhu M. K. <mm...@ya...> - 2003-04-22 16:48:37
|
Nicholas Nethercote wrote: >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. AFAIK, Apache also does it's own mem pooling, which is why I suspect the error is not showing up. Cheerio, M Madhu M Kurup /* Nemo Me Impune Lacessit */ mmk at yahoo-inc dt com |