|
From: Dan K. <da...@ke...> - 2009-04-19 15:01:05
|
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. FWIW this is on a quad CPU ubuntu hardy system. I'll see if it's repeatable. |
|
From: Dan K. <da...@ke...> - 2009-04-19 15:02:01
|
Never mind. Some other child hadn't exited somewhere. On Sun, Apr 19, 2009 at 8:00 AM, Dan Kegel <da...@ke...> 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. > > FWIW this is on a quad CPU ubuntu hardy system. I'll see > if it's repeatable. > |
|
From: Tom H. <to...@co...> - 2009-04-19 15:22:46
|
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 (to...@co...) http://www.compton.nu/ |
|
From: Dan K. <da...@ke...> - 2009-04-19 16:18:34
|
On Sun, Apr 19, 2009 at 8:22 AM, Tom Hughes <to...@co...> wrote: > 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. Yup. (I posted again right away, but it was Too Late :-) |