|
From: Maxim O. <max...@gm...> - 2006-12-06 17:18:52
|
True, this is a custom kernel, and UML. So appreciate any debugging hints. Detailed output is: --402:1:debuglog DebugLog system started by Stage 1, level 2 logging requested --402:1:launcher tool 'memcheck' requested --402:1:launcher selected platform 'x86-linux' --402:1:launcher launching /tmp/vg-3.2.1/lib/valgrind/x86-linux/memcheck --402:1:debuglog DebugLog system started by Stage 2 (main), level 2 logging requested --402:1:main Welcome to Valgrind version 3.2.1 debug logging --402:1:main Checking current stack is plausible --402:1:main Checking initial stack was noted --402:1:main Starting the address space manager --402:2:aspacem sp_at_startup = 0x00BFFADB50 (supplied) --402:2:aspacem minAddr = 0x0004000000 (computed) --402:2:aspacem maxAddr = 0x00BFFACFFF (computed) --402:2:aspacem cStart = 0x0004000000 (computed) --402:2:aspacem vStart = 0x0061FD7000 (computed) --402:2:aspacem suggested_clstack_top = 0x00BEFADFFF (computed) --402:2:aspacem <<< SHOW_SEGMENTS: Initial layout (5 segments, 0 segnames) --402:2:aspacem 0: RSVN 0000000000-0003FFFFFF 64m ----- SmFixed --402:2:aspacem 1: 0004000000-0061FD6FFF 1503m --402:2:aspacem 2: RSVN 0061FD7000-0061FD7FFF 4096 ----- SmFixed --402:2:aspacem 3: 0061FD8000-00BFFACFFF 1503m --402:2:aspacem 4: RSVN 00BFFAD000-00FFFFFFFF 1024m ----- SmFixed --402:2:aspacem >>> --402:2:aspacem Reading /proc/self/maps --402:2:aspacem <<< SHOW_SEGMENTS: With contents of /proc/self/maps (1 segments, 1 segnames) --402:2:aspacem 0: ANON 0000000000-00FFFFFFFF 0 ----- --402:2:aspacem >>> --402:1:main Address space manager is running --402:1:main Starting the dynamic memory manager Valgrind's memory management: out of memory: newSuperblock's request for 1048576 bytes failed. 4294967296 bytes have already been allocated. Valgrind cannot continue. Sorry. On 12/6/06, Julian Seward <js...@ac...> wrote: > > Possibly you have some kind non-standard kernel? > > > Valgrind's memory management: out of memory: > > newSuperblock's request for 1048576 bytes failed. > > 4294967296 bytes have already been allocated. > > Valgrind cannot continue. Sorry. > > Please send the results of a run with flags '-d -d'. > > J > |