[Valgrind-users] Running Valgrind on Android 4.0.4 on PandaBoard

[Martin H. <mar...@ci...>]

Hello,

I would like to run an application under Valgrind on PandaBoard with
Android 4.0.4 built from source (PandaBoard full_eng build).

I have already had success running Valgrind (tools none and memcheck) on
Meizu M9 (its internals are very similar to Google Nexus S) with Android
4.0.3 (stock ROM, rooted) but its memory is quite limited for my needs.

Therefore I tried to repeat the same procedure (I followed the
README.android including the NDK r6 advice) for PandaBoard which has
twice as much memory and faster CPU.

Running any app/command (segfault does not happen for just valgrind
--help) under Valgrind on the PandaBoard however leads to an immediate
segmentation fault as can be seen below when ls was run under Valgrind:

139|root@android:/data/local # ./Inst/bin/valgrind --tool=memcheck ls

==1592== Memcheck, a memory error detector
==1592== Copyright (C) 2002-2011, and GNU GPL'd, by Julian Seward et al.
==1592== Using Valgrind-3.8.0.SVN and LibVEX; rerun with -h for
copyright info
==1592== Command: ls
==1592==
==1592== Invalid read of size 4
==1592==    at 0x400541C: __linker_init (in /system/bin/linker)
==1592==  Address 0x1c is not stack'd, malloc'd or (recently) free'd
==1592==
==1592==
==1592== Process terminating with default action of signal 11 (SIGSEGV)
==1592==  Access not within mapped region at address 0x1C
==1592==    at 0x400541C: __linker_init (in /system/bin/linker)
==1592==  If you believe this happened as a result of a stack
==1592==  overflow in your program's main thread (unlikely but
==1592==  possible), you can try to increase the size of the
==1592==  main thread stack using the --main-stacksize= flag.
==1592==  The main thread stack size used in this run was 8388608.
==1592==
==1592== HEAP SUMMARY:
==1592==     in use at exit: 0 bytes in 0 blocks
==1592==   total heap usage: 0 allocs, 0 frees, 0 bytes allocated
==1592==
==1592== All heap blocks were freed -- no leaks are possible
==1592==
==1592== For counts of detected and suppressed errors, rerun with: -v
==1592== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)
Segmentation fault
139|root@android:/data/local #

Do you have any idea what might be happening?
The crash appears to always happen on the same address, no matter what
application is being run.

Thanks

Martin