|
From: Avery F. <av...@po...> - 2005-05-06 16:06:43
|
On Fri, 2005-05-06 at 08:00 -0500, Nicholas Nethercote wrote: > > That output looks like the program has not yet exited, or Valgrind didn't > detect that it exited. Has the program definitely exited? Is Valgrind > still running? > > I know people have used Valgrind on daemons before, so I'm not aware of > any issues there. Is the program spawning any children -- does it make > any difference if you run with --trace-children=yes ? > > N It turns out the program was forking (I didn't think it was at first because it is largely threaded). valgrind was only watching the original process and not the one doing all the work. I've changed it around and gotten valgrind working now. Thanks, Avery |