|
From: Hrishikesh K. <ris...@gm...> - 2007-02-21 18:23:08
|
Valgrind asserts when run on this platform. Command output : ># ./valgrind -v ls valgrind: m_machine.c:549 (vgPlain_machine_ppc32_set_clszB): Assertion 'szB == 32 || szB == 128' failed. ==1160== at 0x3801AD48: ??? ==1160== by 0x1FFFFFFC: ??? ==1160== by 0x39: ??? ==1160== by 0x38B5B764: ??? ==1160== by 0x38B5B6EC: ??? ==1160== by 0x3801C364: ??? sched status: running_tid=0 Note: see also the FAQ.txt in the source distribution. It contains workarounds to several common problems. If that doesn't help, please report this bug to: www.valgrind.org In the bug report, send all the above text, the valgrind version, and what Linux distro you are using. Thanks. ------------------------------------ ># ./valgrind -d -d ls --1163:1:debuglog DebugLog system started by Stage 1, level 2 logging requested --1163:1:launcher no tool requested, defaulting to 'memcheck' --1163:1:launcher selected platform 'ppc32-linux' --1163:1:launcher launching /data/home/root/lib/valgrind//ppc32-linux/memcheck --1163:1:debuglog DebugLog system started by Stage 2 (main), level 2 logging requested --1163:1:main Welcome to Valgrind version 3.2.3 debug logging --1163:1:main Checking current stack is plausible --1163:1:main Checking initial stack was noted --1163:1:main Starting the address space manager --1163:2:aspacem sp_at_startup = 0x007FFFFC20 (supplied) --1163:2:aspacem minAddr = 0x0004000000 (computed) --1163:2:aspacem maxAddr = 0x007FFFEFFF (computed) --1163:2:aspacem cStart = 0x0004000000 (computed) --1163:2:aspacem vStart = 0x0042000000 (computed) --1163:2:aspacem suggested_clstack_top = 0x007EFFFFFF (computed) --1163:2:aspacem <<< SHOW_SEGMENTS: Initial layout (5 segments, 0 segnames) --1163:2:aspacem 0: RSVN 0000000000-0003FFFFFF 64m ----- SmFixed --1163:2:aspacem 1: 0004000000-0041FFFFFF 992m --1163:2:aspacem 2: RSVN 0042000000-0042000FFF 4096 ----- SmFixed --1163:2:aspacem 3: 0042001000-007FFFEFFF 991m --1163:2:aspacem 4: RSVN 007FFFF000-00FFFFFFFF 2048m ----- SmFixed --1163:2:aspacem >>> --1163:2:aspacem Reading /proc/self/maps --1163:2:aspacem <<< SHOW_SEGMENTS: With contents of /proc/self/maps (11 segments, 1 segnames) --1163:2:aspacem ( 0) /data/home/root/lib/valgrind/ppc32-linux/memcheck --1163:2:aspacem 0: RSVN 0000000000-0003FFFFFF 64m ----- SmFixed --1163:2:aspacem 1: 0004000000-0037FFFFFF 832m --1163:2:aspacem 2: FILE 0038000000-003816CFFF 1495040 r-x-- d=0x303 i=33804 o=0 (0) --1163:2:aspacem 3: 003816D000-003817BFFF 61440 --1163:2:aspacem 4: FILE 003817C000-003817DFFF 8192 rw--- d=0x303 i=33804 o=1490944 (0) --1163:2:aspacem 5: ANON 003817E000-0038CF7FFF 11m rwx-- --1163:2:aspacem 6: 0038CF8000-0041FFFFFF 147m --1163:2:aspacem 7: RSVN 0042000000-0042000FFF 4096 ----- SmFixed --1163:2:aspacem 8: 0042001000-007FFFEFFF 991m --1163:2:aspacem 9: ANON 007FFFF000-007FFFFFFF 4096 rwx-- --1163:2:aspacem 10: RSVN 0080000000-00FFFFFFFF 2048m ----- SmFixed --1163:2:aspacem >>> --1163:1:main Address space manager is running --1163:1:main Starting the dynamic memory manager --1163:1:mallocfr newSuperblock at 0x42001000 (pszB 1048560) owner VALGRIND/tool --1163:1:main Dynamic memory manager is running --1163:1:main Getting stage1's name --1163:1:main Get hardware capabilities ... --1163:1:main ... arch = PPC32, hwcaps = ppc32-int-flt-GX --1163:1:main Split up command line --1163:1:main Preprocess command line opts --1163:1:main Loading client --1163:1:main Setup client env --1163:2:main preload_string: --1163:2:main "/data/home/root/lib/valgrind//ppc32-linux/vgpreload_core.so:/data/home/root/lib/valgrind//ppc32-linux/vgpreload_memcheck.so" --1163:1:main Setup client stack valgrind: m_machine.c:549 (vgPlain_machine_ppc32_set_clszB): Assertion 'szB == 32 || szB == 128' failed. ==1163== at 0x3801AD48: ??? ==1163== by 0x1FFFFFFC: ??? ==1163== by 0x39: ??? ==1163== by 0x38B5B764: ??? ==1163== by 0x38B5B6EC: ??? ==1163== by 0x3801C364: ??? sched status: running_tid=0 |
|
From: Julian S. <js...@ac...> - 2007-02-23 10:24:36
|
On Wednesday 21 February 2007 18:23, Hrishikesh Kulkarni wrote: > Valgrind asserts when run on this platform. > > Command output : > ># ./valgrind -v ls > > valgrind: m_machine.c:549 (vgPlain_machine_ppc32_set_clszB): Assertion 'szB > == 32 || szB == 128' failed. There may be more than one such assertion. What I suggest is you add the 256 case to this assertion, rebuild, retry, etc, until you get something that works. Then send the resulting patch. What CPU is this on? I know of no PPC cpus with 256 byte line sizes. J |