OpenWrt Forum Archive

Topic: Valgrind + MIPS 24KEc + Kernel 3.18.21 + MUSL

The content of this topic has been archived on 1 May 2018. There are no obvious gaps in this topic, but there may still be some posts missing at the end.

Hello.

I can't seem to get the Valgrind + MIPS 24KEc + Kernel 3.18.21 + MUSL combination to work on our embedded system. 3.10.1 and 3.11 just sit there hung when running a dead simple "hello world" program:

 

 valgrind --leak_check=yes ./hello

And if I take 3.12 and apply the 3.11 patches to it, I get output, but everything sefaults.

root@DA-FE:/usr/local/bin# valgrind --leak-check=yes ./hello 
==3915== Memcheck, a memory error detector
==3915== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.
==3915== Using Valgrind-3.12.0 and LibVEX; rerun with -h for copyright info
==3915== Command: ./hello
==3915== 
==3915== Invalid read of size 4
==3915==    at 0x48C3154: free (in /usr/lib/valgrind/vgpreload_memcheck-mips32-linux.so)
==3915==    by 0x4088C04: ??? (in /lib/libc.so)
==3915==  Address 0x1e0d8 is not stack'd, malloc'd or (recently) free'd
==3915== 
==3915== 
==3915== Process terminating with default action of signal 11 (SIGSEGV)
==3915==  Access not within mapped region at address 0x1E0D8
==3915==    at 0x48C3154: free (in /usr/lib/valgrind/vgpreload_memcheck-mips32-linux.so)
==3915==    by 0x4088C04: ??? (in /lib/libc.so)
==3915==  If you believe this happened as a result of a stack
==3915==  overflow in your program's main thread (unlikely but
==3915==  possible), you can try to increase the size of the
==3915==  main thread stack using the --main-stacksize= flag.
==3915==  The main thread stack size used in this run was 8388608.
==3915== 
==3915== HEAP SUMMARY:
==3915==     in use at exit: 0 bytes in 0 blocks
==3915==   total heap usage: 0 allocs, 0 frees, 0 bytes allocated
==3915== 
==3915== All heap blocks were freed -- no leaks are possible
==3915== 
==3915== For counts of detected and suppressed errors, rerun with: -v
==3915== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)
Segmentation fault

What dark magic must I do to access Valgrind power on MUSL/MIPS ?

Thanks!

Oh, we're using a version of Designated Driver we snapped about a year ago -- with the odd mods and updates, but MUSL is at 1.1.12.

The discussion might have continued from here.