==2910== Memcheck, a memory error detector ==2910== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al. ==2910== Using Valgrind-3.10.0 and LibVEX; rerun with -h for copyright info ==2910== Command: binutils-gdb/binutils/objdump -afphxgGtTrRwW --special-syms 3371-1520-0.004 ==2910== Parent PID: 3867 ==2910== ==2910== Invalid read of size 8 ==2910== at 0x40C51D: dump_reloc_set (objdump.c:3017) ==2910== by 0x40DBB2: dump_relocs_in_section (objdump.c:3132) ==2910== by 0x50188B: bfd_map_over_sections (section.c:1354) ==2910== by 0x40D2AD: dump_relocs (objdump.c:3141) ==2910== by 0x40D2AD: dump_bfd (objdump.c:3267) ==2910== by 0x40D6EF: display_object_bfd (objdump.c:3330) ==2910== by 0x40D6EF: display_any_bfd (objdump.c:3404) ==2910== by 0x40F7B2: display_file (objdump.c:3425) ==2910== by 0x40A079: main (objdump.c:3707) ==2910== Address 0x133da48 is not stack'd, malloc'd or (recently) free'd ==2910== ==2910== ==2910== Process terminating with default action of signal 11 (SIGSEGV) ==2910== Access not within mapped region at address 0x133DA48 ==2910== at 0x40C51D: dump_reloc_set (objdump.c:3017) ==2910== by 0x40DBB2: dump_relocs_in_section (objdump.c:3132) ==2910== by 0x50188B: bfd_map_over_sections (section.c:1354) ==2910== by 0x40D2AD: dump_relocs (objdump.c:3141) ==2910== by 0x40D2AD: dump_bfd (objdump.c:3267) ==2910== by 0x40D6EF: display_object_bfd (objdump.c:3330) ==2910== by 0x40D6EF: display_any_bfd (objdump.c:3404) ==2910== by 0x40F7B2: display_file (objdump.c:3425) ==2910== by 0x40A079: main (objdump.c:3707) ==2910== If you believe this happened as a result of a stack ==2910== overflow in your program's main thread (unlikely but ==2910== possible), you can try to increase the size of the ==2910== main thread stack using the --main-stacksize= flag. ==2910== The main thread stack size used in this run was 8388608. ==2910== ==2910== HEAP SUMMARY: ==2910== in use at exit: 52,401 bytes in 23 blocks ==2910== total heap usage: 59 allocs, 36 frees, 132,977 bytes allocated ==2910== ==2910== LEAK SUMMARY: ==2910== definitely lost: 0 bytes in 0 blocks ==2910== indirectly lost: 0 bytes in 0 blocks ==2910== possibly lost: 0 bytes in 0 blocks ==2910== still reachable: 52,401 bytes in 23 blocks ==2910== suppressed: 0 bytes in 0 blocks ==2910== Rerun with --leak-check=full to see details of leaked memory ==2910== ==2910== For counts of detected and suppressed errors, rerun with: -v ==2910== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 1 from 1)