|
From: Igmar P. <mai...@jd...> - 2006-05-03 06:36:34
|
> Thanks, it compiles fine now, however it crashes on PPC target. A > problem to this effect > has already been reported : > > http://sourceforge.net/mailarchive/forum.php?thread_id=10079534&forum_id=32038 Looks unrelated to me, this was a issue of a CPU feature detection not working as intended AFAIK. > though on a QEMU image. What I see is : > ./valgrind /bin/ls > ==795== Memcheck, a memory error detector. > ==795== Copyright (C) 2002-2005, and GNU GPL'd, by Julian Seward et al. > ==795== Using LibVEX rev 1575, a library for dynamic binary translation. > ==795== Copyright (C) 2004-2005, and GNU GPL'd, by OpenWorks LLP. > ==795== Using valgrind-3.1.1, a dynamic binary instrumentation framework. > ==795== Copyright (C) 2000-2005, and GNU GPL'd, by Julian Seward et al. > ==795== For more details, rerun with: -v > ==795== > ==795== > ==795== Process terminating with default action of signal 11 (SIGSEGV) > ==795== Bad permissions for mapped region at address 0x4024BF4 > ==795== at 0x4024BF4: ??? > ==795== by 0x40100E4: (within /lib/ld-2.2.5.so) > ==795== > ==795== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) > ==795== malloc/free: in use at exit: 0 bytes in 0 blocks. > ==795== malloc/free: 0 allocs, 0 frees, 0 bytes allocated. > ==795== For counts of detected errors, rerun with: -v > ==795== All heap blocks were freed -- no leaks are possible. > Segmentation fault > > I had already done what Julian had asked for in the above mentioned > thread, however the > crash persists. Are there any workarounds ? I am having a 2.4.20 kernel > running on target > with glibc 2.2 (and ofcourse crosscompiled valgrind with gcc2.96 ;)). You might want to try a strace of the binary and post it here, so someone can look at what is actually going on. Igmar |