Valgrind crash on Texas Instrument AM3352 (armv7le) and QNX

Cédric Perles <[email protected]>
Newsgroups gmane.comp.debugging.valgrind
Message-ID <PR1P264MB43584988249B92E83809411AE2879@PR1P264MB4358.FRAP264.PROD.OUTLOOK.COM>
Hi Valgrind community,

I have 2 different boards running QNX 6.5 and mounting the exact same file system.
One board is based on an NXP iMX53 SoC and the other one on a Texas Instrument AM3352.
Since both SoC share the same instruction set (Cortex A8 - amv7le), they can run the same binaries.

However, whereas Valgrind 3.10.1 is working perfectly on the iMX53, it crashes on the AM3352 :

pendant:/bin>/usr/bin/valgrind --tool=memcheck --allow-mismatched-debuginfo=yes --extra-debuginfo-path=/usr/lib/debug/ echo
==1863697== Memcheck, a memory error detector
==1863697== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al.
==1863697== Using Valgrind-3.10.1 and LibVEX; rerun with -h for copyright info
==1863697== Command: echo
==1863697==
==1863697==
==1863697== Process terminating with default action of signal 11 (SIGSEGV): dumping core
==1863697==  Bad permissions for mapped region at address 0x245C
==1863697==    at 0x1E4CC: mprotect (mprotect.c:33 in /proc/boot/libc.so.3)
==1863697==    by 0x25B03: _band_get_aligned (band.c:450 in /proc/boot/libc.so.3)
==1863697==    by 0x77383: ??? (in /proc/boot/libc.so.3)
==1863697==
==1863697== HEAP SUMMARY:
==1863697==     in use at exit: 0 bytes in 0 blocks
==1863697==   total heap usage: 0 allocs, 0 frees, 0 bytes allocated
==1863697==
==1863697== All heap blocks were freed -- no leaks are possible
==1863697==
==1863697== For counts of detected and suppressed errors, rerun with: -v
==1863697== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
Memory fault

It always crashes the same way, whatever the binary I analyse.

I am clueless, I don't understand how it can work on iMX53 and fail on AM3352 with the same file system (same binaries, same libs, same scripts, same conf ...).
Does somebody have an idea ?

Best regards,

Cédric
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.