On Friday 09 January 2009, Matthew Clark wrote: > Below is the valgrind run with the trace-signals enabled.
> --21465-- signal 11 arrived ... si_code=2, EIP=0xffe266c, eip=0x428abe48 > --21465-- SIGSEGV: si_code=2 faultaddr=0x3818eef8 tid=1 ESP=0x7e981fe0 > seg=0x38042000-0x381cefff > --21465-- delivering signal 11 (SIGSEGV):2 to thread 1 > --21465-- delivering 11 (code 2) to default handler; action: terminate+core > ==21465== > ==21465== Process terminating with default action of signal 11 (SIGSEGV) > ==21465== Bad permissions for mapped region at address 0x3818EEF8 > ==21465== at 0xFFE266C: (within /lib/ld-2.3.6.so) > --21465:1:aspacem <<< SHOW_SEGMENTS: Memory layout at client shutdown > (32 segments, 3 segnames) > --21465:1:aspacem ( 0) /usr/local/lib/valgrind/ppc32-linux/memcheck > --21465:1:aspacem ( 1) /bin/ls > --21465:1:aspacem ( 2) /lib/ld-2.3.6.so > --21465:1:aspacem 13: FILE 0038000000-0038040fff 266240 r-x-- d=0x00c > i=4567521 o=0 (0) > --21465:1:aspacem 14: file 0038041000-0038041fff 4096 r-x-- d=0x00c > i=4567521 o=266240 (0) > --21465:1:aspacem 15: FILE 0038042000-00381cefff 1626112 r-x-- d=0x00c > i=4567521 o=270336 (0) There's clearly some kind of permissions problem to do with the tool executable itself (/usr/local/lib/valgrind/ppc32-linux/memcheck) since the fault address is within that. However, without being able to reproduce this it's hard to see how to make further progress. I haven't seen or heard of any such problem on other ppc linuxes, so I wonder if this is a distribution-specific oddity. J ------------------------------------------------------------------------------ Check out the new SourceForge.net Marketplace. It is the best place to buy or sell services for just about anything Open Source. http://p.sf.net/sfu/Xq1LFB _______________________________________________ Valgrind-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/valgrind-users
