|
From: Christian P. <tr...@ge...> - 2005-07-20 14:47:38
|
On Wednesday 20 July 2005 15:39, Nicholas Nethercote wrote: > 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 traversi= ng > > 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 */ > > > > ) =3D 0 > > mmap(0x3c3c34b00000, 74507940265984, PROT_NONE, > > MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS|MAP_NORESERVE, -1, 0 > > > > /* it freezes again */ > > > > ) =3D 0x3c3c34b00000 > > > > ... > > > > write(1, "usage: valgrind --tool=3D<toolname"..., 90usage: valgrind > > --tool=3D<toolname> [options] prog-and-args > > > > /* ... */ > > > > exit_group(0) =3D ? > > > > /* 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? I'm having 2GB RAM, and 1GB swap. maybe this matters? Besides, why the hell is valgrind m[un]mapping such a huge space (I even=20 haven't that much RAM et al) > Can you re-run with "valgrind -d" and post the output? Thanks. simple "valgrind -d" (without any other args)? hmm... hold on... run of $(valgrind -d): =2D-22000:1:debuglog DebugLog system started by Stage 1, level 1 logging=20 requested =2D-22000:1:stage1 main(): running main2() on new stack =2D-22000:1:stage1 main2(): starting stage2 =2D-22000:1:debuglog DebugLog system started by Stage 2 (main), level 1 log= ging=20 requested =2D-22000:1:main Doing scan_auxv() =2D-22000:1:main Preprocess command line opts =2D-22000:1:main Loading tool =2D-22000:1:main Laying out remaining space /* big big sleep */ =2D-22000:1:main Loading client valgrind: no program specified valgrind: Use --help for more information. /* big big sleep */ /* return to terminal */ Hope this helps, Christian Parpart. |