==9534== Memcheck, a memory error detector ==9534== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al. ==9534== Using Valgrind-3.10.0 and LibVEX; rerun with -h for copyright info ==9534== Command: binutils-gdb/binutils/objdump -afphxgGtTrRwW --special-syms samples/9609b8d6 ==9534== Parent PID: 9533 ==9534== ==9534== Invalid read of size 1 ==9534== at 0x529BF00: vfprintf (vfprintf.c:1636) ==9534== by 0x52A45C8: printf (printf.c:33) ==9534== by 0x40B8BA: dump_reloc_set (objdump.c:3081) ==9534== by 0x40E3EA: dump_relocs_in_section (objdump.c:3166) ==9534== by 0x50019B: bfd_map_over_sections (section.c:1354) ==9534== by 0x40D59D: dump_relocs (objdump.c:3175) ==9534== by 0x40D59D: dump_bfd (objdump.c:3301) ==9534== by 0x40DF27: display_object_bfd (objdump.c:3364) ==9534== by 0x40DF27: display_any_bfd (objdump.c:3446) ==9534== by 0x40FEA2: display_file (objdump.c:3467) ==9534== by 0x40A849: main (objdump.c:3749) ==9534== Address 0xffffffff is not stack'd, malloc'd or (recently) free'd ==9534== ==9534== ==9534== Process terminating with default action of signal 11 (SIGSEGV) ==9534== Access not within mapped region at address 0xFFFFFFFF ==9534== at 0x529BF00: vfprintf (vfprintf.c:1636) ==9534== by 0x52A45C8: printf (printf.c:33) ==9534== by 0x40B8BA: dump_reloc_set (objdump.c:3081) ==9534== by 0x40E3EA: dump_relocs_in_section (objdump.c:3166) ==9534== by 0x50019B: bfd_map_over_sections (section.c:1354) ==9534== by 0x40D59D: dump_relocs (objdump.c:3175) ==9534== by 0x40D59D: dump_bfd (objdump.c:3301) ==9534== by 0x40DF27: display_object_bfd (objdump.c:3364) ==9534== by 0x40DF27: display_any_bfd (objdump.c:3446) ==9534== by 0x40FEA2: display_file (objdump.c:3467) ==9534== by 0x40A849: main (objdump.c:3749) ==9534== If you believe this happened as a result of a stack ==9534== overflow in your program's main thread (unlikely but ==9534== possible), you can try to increase the size of the ==9534== main thread stack using the --main-stacksize= flag. ==9534== The main thread stack size used in this run was 8388608. ==9534== ==9534== HEAP SUMMARY: ==9534== in use at exit: 148,835 bytes in 40 blocks ==9534== total heap usage: 100 allocs, 60 frees, 360,329 bytes allocated ==9534== ==9534== LEAK SUMMARY: ==9534== definitely lost: 0 bytes in 0 blocks ==9534== indirectly lost: 0 bytes in 0 blocks ==9534== possibly lost: 0 bytes in 0 blocks ==9534== still reachable: 148,835 bytes in 40 blocks ==9534== suppressed: 0 bytes in 0 blocks ==9534== Rerun with --leak-check=full to see details of leaked memory ==9534== ==9534== For counts of detected and suppressed errors, rerun with: -v ==9534== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)