|
From: Joerg B. <j....@we...> - 2003-04-22 07:53:06
|
Nicholas Nethercote <nj...@ca...> schrieb am 22.04.03 09:47:45:
>
> 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
>
nope, I told apache not to spawn (for the sake of debugging), it the -X
option for apache.
Joerg
|
|
From: Nicholas N. <nj...@ca...> - 2003-04-22 07:59:03
|
On Tue, 22 Apr 2003, Joerg Beyer wrote: > > 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. > > nope, I told apache not to spawn (for the sake of debugging), it the -X > option for apache. Did you try --trace-children=yes? Is your program *not* invoked with a script? 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 startup message? Have you tried Valgrind with other programs, eg. small test ones that have deliberate errors in them? What version of Valgrind are you using? N |