|
From: Sasikanth b. <sas...@gm...> - 2014-08-07 08:26:31
|
Hi all,
I had checked-out latest valgrind code from svn repo and cross-compiled
it for octeon. Looks the instruction errors seems fixed but I still
see the following issue. And Libc has the debugging symbols.
/lib64/libc-2.11.1.so: ELF 64-bit MSB shared object, MIPS, MIPS64 rel2
version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux
2.6.34, not stripped
Any suggestions?
valgrind --run-libc-freeres=no ./a.out 1
==1409== Memcheck, a memory error detector
==1409== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al.
==1409== Using Valgrind-3.10.0.SVN and LibVEX; rerun with -h for copyright
info
==1409== Command: ./a.out 1
==1409==
1409:
==1409==
==1409== Process terminating with default action of signal 11 (SIGSEGV)
==1409== Access not within mapped region at address 0x50
==1409== at 0x400D148: _dl_relocate_object (dl-machine.h:713)
==1409== by 0x4004B50: dl_main (rtld.c:2227)
==1409== by 0x4019188: _dl_sysdep_start (dl-sysdep.c:243)
==1409== by 0x40021A4: _dl_start_final (rtld.c:333)
==1409== by 0x40023E4: _dl_start (rtld.c:561)
==1409== by 0x4001C0C: __start (in /lib64/ld-2.11.1.so)
==1409== If you believe this happened as a result of a stack
==1409== overflow in your program's main thread (unlikely but
==1409== possible), you can try to increase the size of the
==1409== main thread stack using the --main-stacksize= flag.
==1409== The main thread stack size used in this run was 8388608.
==1409==
==1409== HEAP SUMMARY:
==1409== in use at exit: 0 bytes in 0 blocks
==1409== total heap usage: 0 allocs, 0 frees, 0 bytes allocated
==1409==
==1409== All heap blocks were freed -- no leaks are possible
==1409==
==1409== For counts of detected and suppressed errors, rerun with: -v
==1409== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 4 from 4)
Segmentation fault
|
|
From: Petar J. <mip...@gm...> - 2014-08-07 17:20:07
|
Hi Sasi, Support for Cavium specific extensions in Valgrind is not complete today. If you want to use Valgrind on a Cavium board, I suggest you put vanilla MIPS64 rootfs and build Valgrind with a standard GCC for MIPS64. That environment has been tested and has no known issues (so far). However, if you still want to stick with Cavium specific toolchain and rootfs, be aware that you are likely to come across issues specific to Cavium extensions that are - as I previously said - not fully supported yet. In that case, I suggest you: 1. create a Bugzilla issue [1] and report your findings, 2. be able to provide feedback and - wait till the issue is fixed. That would be all. Regards, Petar [1] KDE Bugzilla, https://bugs.kde.org/ On Thu, Aug 7, 2014 at 10:26 AM, Sasikanth babu <sas...@gm...> wrote: > Hi all, > > I had checked-out latest valgrind code from svn repo and cross-compiled > it for octeon. Looks the instruction errors seems fixed but I still > see the following issue. And Libc has the debugging symbols. > > /lib64/libc-2.11.1.so: ELF 64-bit MSB shared object, MIPS, MIPS64 rel2 > version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux > 2.6.34, not stripped > > Any suggestions? > > valgrind --run-libc-freeres=no ./a.out 1 > ==1409== Memcheck, a memory error detector > ==1409== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al. > ==1409== Using Valgrind-3.10.0.SVN and LibVEX; rerun with -h for copyright > info > ==1409== Command: ./a.out 1 > ==1409== > 1409: > ==1409== > ==1409== Process terminating with default action of signal 11 (SIGSEGV) > ==1409== Access not within mapped region at address 0x50 > ==1409== at 0x400D148: _dl_relocate_object (dl-machine.h:713) > ==1409== by 0x4004B50: dl_main (rtld.c:2227) > ==1409== by 0x4019188: _dl_sysdep_start (dl-sysdep.c:243) > ==1409== by 0x40021A4: _dl_start_final (rtld.c:333) > ==1409== by 0x40023E4: _dl_start (rtld.c:561) > ==1409== by 0x4001C0C: __start (in /lib64/ld-2.11.1.so) > ==1409== If you believe this happened as a result of a stack > ==1409== overflow in your program's main thread (unlikely but > ==1409== possible), you can try to increase the size of the > ==1409== main thread stack using the --main-stacksize= flag. > ==1409== The main thread stack size used in this run was 8388608. > ==1409== > ==1409== HEAP SUMMARY: > ==1409== in use at exit: 0 bytes in 0 blocks > ==1409== total heap usage: 0 allocs, 0 frees, 0 bytes allocated > ==1409== > ==1409== All heap blocks were freed -- no leaks are possible > ==1409== > ==1409== For counts of detected and suppressed errors, rerun with: -v > ==1409== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 4 from 4) > Segmentation fault > > > > ------------------------------------------------------------------------------ > Infragistics Professional > Build stunning WinForms apps today! > Reboot your WinForms applications with our WinForms controls. > Build a bridge from your legacy apps to the future. > > http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk > _______________________________________________ > Valgrind-developers mailing list > Val...@li... > https://lists.sourceforge.net/lists/listinfo/valgrind-developers > > |