==10637== Memcheck, a memory error detector ==10637== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al. ==10637== Using Valgrind-3.10.0 and LibVEX; rerun with -h for copyright info ==10637== Command: binutils-gdb/binutils/objdump -afphxgGtTrRwW --special-syms samples/b80c9636 ==10637== Parent PID: 10636 ==10637== ==10637== Warning: set address range perms: large range [0x59fd040, 0x359fd050) (undefined) ==10637== Invalid write of size 1 ==10637== at 0x83CDB5: process_otr (versados.c:405) ==10637== by 0x83D82F: versados_pass_2 (versados.c:666) ==10637== by 0x83D9D4: versados_canonicalize_symtab (versados.c:726) ==10637== by 0x40D3F3: slurp_symtab (objdump.c:573) ==10637== by 0x40D3F3: dump_bfd (objdump.c:3276) ==10637== by 0x40DF27: display_object_bfd (objdump.c:3364) ==10637== by 0x40DF27: display_any_bfd (objdump.c:3446) ==10637== by 0x40FEA2: display_file (objdump.c:3467) ==10637== by 0x40A849: main (objdump.c:3749) ==10637== Address 0x3fd100b7 is not stack'd, malloc'd or (recently) free'd ==10637== ==10637== ==10637== Process terminating with default action of signal 11 (SIGSEGV) ==10637== Access not within mapped region at address 0x3FD100B7 ==10637== at 0x83CDB5: process_otr (versados.c:405) ==10637== by 0x83D82F: versados_pass_2 (versados.c:666) ==10637== by 0x83D9D4: versados_canonicalize_symtab (versados.c:726) ==10637== by 0x40D3F3: slurp_symtab (objdump.c:573) ==10637== by 0x40D3F3: dump_bfd (objdump.c:3276) ==10637== by 0x40DF27: display_object_bfd (objdump.c:3364) ==10637== by 0x40DF27: display_any_bfd (objdump.c:3446) ==10637== by 0x40FEA2: display_file (objdump.c:3467) ==10637== by 0x40A849: main (objdump.c:3749) ==10637== If you believe this happened as a result of a stack ==10637== overflow in your program's main thread (unlikely but ==10637== possible), you can try to increase the size of the ==10637== main thread stack using the --main-stacksize= flag. ==10637== The main thread stack size used in this run was 8388608. ==10637== ==10637== HEAP SUMMARY: ==10637== in use at exit: 805,315,511 bytes in 22 blocks ==10637== total heap usage: 33 allocs, 11 frees, 805,364,845 bytes allocated ==10637== ==10637== LEAK SUMMARY: ==10637== definitely lost: 16 bytes in 8 blocks ==10637== indirectly lost: 0 bytes in 0 blocks ==10637== possibly lost: 0 bytes in 0 blocks ==10637== still reachable: 805,315,495 bytes in 14 blocks ==10637== suppressed: 0 bytes in 0 blocks ==10637== Rerun with --leak-check=full to see details of leaked memory ==10637== ==10637== For counts of detected and suppressed errors, rerun with: -v ==10637== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)