Dan Kegel wrote: > I'm staring at what looks like a hung valgrind job: > > dank 1259 16.8 12.9 401756 233348 pts/1 Sl 07:27 4:43 > valgrind --smc-check=all --leak-check=full --num-callers=30 > --trace-children=yes --xml=yes > --suppressions=/home/dank/chromium/src/tools/valgrind/suppressions.txt > --suppressions=/home/dank/chromium/src/chrome/test/data/valgrind/suppressions.txt > --log-file=valgrind.tmp/valgrind.%p > /home/dank/chromium/src/sconsbuild/Debug/chrome ... > dank 1264 1.0 0.0 0 0 pts/1 Z 07:27 0:18 > [memcheck-x86-li] <defunct> > > It kind of looks like valgrind launched memcheck, but then > didn't notice when memcheck exited. It's been hung for > many minutes.
I think you're confused about how valgrind works - the launcher doesn't fork memcheck and then wait for it, it just execs it so that memcheck replaces the launcher. I suspect what you actually have is a child valgrind that is a result of a valgrinded process forking. In which case any waiting and suchlike is a property of the application being valgrinded and not of valgrind. Tom -- Tom Hughes ([email protected]) http://www.compton.nu/ ------------------------------------------------------------------------------ Stay on top of everything new and different, both inside and around Java (TM) technology - register by April 22, and save $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco. 300 plus technical and hands-on sessions. Register today. Use priority code J9JMT32. http://p.sf.net/sfu/p _______________________________________________ Valgrind-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/valgrind-users
