|
From: Nicholas N. <nj...@cs...> - 2005-07-20 13:39:27
|
On Wed, 20 Jul 2005, Christian Parpart wrote: > below is an extract of $(strace valgrind --help); It took me about 2 > minutes or so to see the output, well, at least, very long. Although, a > $(ps ax) on another terminal in parralel seems to freeze while traversing > through the process list. $(top) shows valgrind to be using 98% of my CPU. > > /* below follows the obove mentioned output (stripped) */ > > munmap(0, 66229278605312 > > /* here it freeyes for about 20 seconds */ > > ) = 0 > mmap(0x3c3c34b00000, 74507940265984, PROT_NONE, > MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS|MAP_NORESERVE, -1, 0 > > /* it freezes again */ > > ) = 0x3c3c34b00000 > > ... > > write(1, "usage: valgrind --tool=<toolname"..., 90usage: valgrind > --tool=<toolname> [options] prog-and-args > > /* ... */ > > exit_group(0) = ? > > /* again, it freezes, and then returns to command prompt */ > > NOW, I'd be happy when someone tells me that this is a known issue and is > gonna be fixed right the way (before 3.0.0 hits the line) I haven't seen this one. The mmap and munmap calls are very big -- 61680GB and 69390GB respectively. The fact that it happens before the usage message shows this is happening very early. I guess these mmap/munmap calls are from the start-up padding, but then the question is why isn't this causing problems on other AMD64 systems? Can you re-run with "valgrind -d" and post the output? Thanks. N |