Menu
▾
▴
[Valgrind-users] Valgrind: FATAL: aspacem assertion failed:
|
From: john <joh...@cl...> - 2015-04-15 08:50:44
|
Hi, I am trying to run valgrind on an embedded arm device without success. The system is built using buildroot-2013.05. The system specifications are given below the following vargrind output: # valgrind -d -d --2993:1:debuglog DebugLog system started by Stage 1, level 2 logging requested --2993:1:launcher no tool requested, defaulting to 'memcheck' --2993:1:launcher no client specified, defaulting platform to 'arm-linux' --2993:1:launcher launching /usr/lib/valgrind/memcheck-arm-linux --2993:1:debuglog DebugLog system started by Stage 2 (main), level 2 logging requested --2993:1:main Welcome to Valgrind version 3.8.1 debug logging --2993:1:main Checking current stack is plausible --2993:1:main Checking initial stack was noted --2993:1:main Starting the address space manager --2993:2:aspacem sp_at_startup = 0x00beeead70 (supplied) --2993:2:aspacem minAddr = 0x0004000000 (computed) --2993:2:aspacem maxAddr = 0x00beee9fff (computed) --2993:2:aspacem cStart = 0x0004000000 (computed) --2993:2:aspacem vStart = 0x0061775000 (computed) --2993:2:aspacem suggested_clstack_top = 0x00bdeeafff (computed) --2993:2:aspacem <<< SHOW_SEGMENTS: Initial layout (5 segments, 0 segnames) --2993:2:aspacem 0: RSVN 0000000000-0003ffffff 64m ----- SmFixed --2993:2:aspacem 1: 0004000000-0061774fff 1495m --2993:2:aspacem 2: RSVN 0061775000-0061775fff 4096 ----- SmFixed --2993:2:aspacem 3: 0061776000-00beee9fff 1495m --2993:2:aspacem 4: RSVN 00beeea000-00ffffffff 1041m ----- SmFixed --2993:2:aspacem >>> --2993:2:aspacem Reading /proc/self/maps --2993:0:aspacem -1: ANON 0038000000-00382a5fff 2777088 r-x-- SmFixed d=0x000 i=8527 o=32768 (0) m=0 /usr/lib/valgrind/memcheck-arm-linux --2993:0:aspacem Valgrind: FATAL: aspacem assertion failed: --2993:0:aspacem segment_is_sane --2993:0:aspacem at m_aspacemgr/aspacemgr-linux.c:1477 (add_segment) --2993:0:aspacem Exiting now. My /proc/self/maps is as follows: -------------------------- 00008000-00106000 r-xp 00000000 00:00 8773 /bin/busybox 0010e000-0010f000 rw-p 000fe000 00:00 8773 /bin/busybox 0010f000-00111000 rw-p 00000000 00:00 0 [heap] b6dae000-b6eea000 r-xp 00000000 00:00 8937 /lib/libc-2.13.so b6eea000-b6ef2000 ---p 0013c000 00:00 8937 /lib/libc-2.13.so b6ef2000-b6ef4000 r--p 0013c000 00:00 8937 /lib/libc-2.13.so b6ef4000-b6ef5000 rw-p 0013e000 00:00 8937 /lib/libc-2.13.so b6ef5000-b6ef8000 rw-p 00000000 00:00 0 b6ef8000-b6f66000 r-xp 00000000 00:00 8935 /lib/libm-2.13.so b6f66000-b6f6d000 ---p 0006e000 00:00 8935 /lib/libm-2.13.so b6f6d000-b6f6e000 r--p 0006d000 00:00 8935 /lib/libm-2.13.so b6f6e000-b6f6f000 rw-p 0006e000 00:00 8935 /lib/libm-2.13.so b6f6f000-b6f8f000 r-xp 00000000 00:00 8945 /lib/ld-2.13.so b6f91000-b6f92000 rw-p 00000000 00:00 0 b6f94000-b6f95000 rw-p 00000000 00:00 0 b6f95000-b6f96000 r-xp 00000000 00:00 0 [sigpage] b6f96000-b6f97000 r--p 0001f000 00:00 8945 /lib/ld-2.13.so b6f97000-b6f98000 rw-p 00020000 00:00 8945 /lib/ld-2.13.so bee7c000-bee9d000 rw-p 00000000 00:00 0 [stack] ffff0000-ffff1000 r-xp 00000000 00:00 0 [vectors] ---------------------------------------------- # cat /proc/cpuinfo processor : 0 model name : ARMv7 Processor rev 0 (v7l) Features : swp half thumb fastmult vfp edsp neon vfpv3 tls vfpd32 CPU implementer : 0x41 CPU architecture: 7 CPU variant : 0x3 CPU part : 0xc09 CPU revision : 0 processor : 1 model name : ARMv7 Processor rev 0 (v7l) Features : swp half thumb fastmult vfp edsp neon vfpv3 tls vfpd32 CPU implementer : 0x41 CPU architecture: 7 CPU variant : 0x3 CPU part : 0xc09 CPU revision : 0 Hardware : Xilinx Zynq Platform Revision : 0000 Serial : 0000000000000000 ---------------------------------------------------------- Any suggestions on what the issue might be or where I should start looking regards beckett |
