==20487== Memcheck, a memory error detector ==20487== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al. ==20487== Using Valgrind-3.10.0 and LibVEX; rerun with -h for copyright info ==20487== Command: binutils-gdb/binutils/objdump -x 030-247858-0.001:0.1 ==20487== Parent PID: 14700 ==20487== ==20487== Invalid read of size 1 ==20487== at 0x52981B2: vfprintf (vfprintf.c:1649) ==20487== by 0x52A06C6: fprintf (fprintf.c:32) ==20487== by 0x46D361: _bfd_elf_print_private_bfd_data (elf.c:1408) ==20487== by 0x4078EE: dump_bfd_private_header (objdump.c:2648) ==20487== by 0x4078EE: dump_bfd (objdump.c:3223) ==20487== by 0x407F1F: display_object_bfd (objdump.c:3322) ==20487== by 0x407F1F: display_any_bfd (objdump.c:3396) ==20487== by 0x409FD2: display_file (objdump.c:3417) ==20487== by 0x4048F9: main (objdump.c:3699) ==20487== Address 0x7cc is not stack'd, malloc'd or (recently) free'd ==20487== ==20487== ==20487== Process terminating with default action of signal 11 (SIGSEGV) ==20487== Access not within mapped region at address 0x7CC ==20487== at 0x52981B2: vfprintf (vfprintf.c:1649) ==20487== by 0x52A06C6: fprintf (fprintf.c:32) ==20487== by 0x46D361: _bfd_elf_print_private_bfd_data (elf.c:1408) ==20487== by 0x4078EE: dump_bfd_private_header (objdump.c:2648) ==20487== by 0x4078EE: dump_bfd (objdump.c:3223) ==20487== by 0x407F1F: display_object_bfd (objdump.c:3322) ==20487== by 0x407F1F: display_any_bfd (objdump.c:3396) ==20487== by 0x409FD2: display_file (objdump.c:3417) ==20487== by 0x4048F9: main (objdump.c:3699) ==20487== If you believe this happened as a result of a stack ==20487== overflow in your program's main thread (unlikely but ==20487== possible), you can try to increase the size of the ==20487== main thread stack using the --main-stacksize= flag. ==20487== The main thread stack size used in this run was 8388608. ==20487== ==20487== HEAP SUMMARY: ==20487== in use at exit: 32,293 bytes in 14 blocks ==20487== total heap usage: 23 allocs, 9 frees, 69,255 bytes allocated ==20487== ==20487== LEAK SUMMARY: ==20487== definitely lost: 0 bytes in 0 blocks ==20487== indirectly lost: 0 bytes in 0 blocks ==20487== possibly lost: 0 bytes in 0 blocks ==20487== still reachable: 32,293 bytes in 14 blocks ==20487== suppressed: 0 bytes in 0 blocks ==20487== Rerun with --leak-check=full to see details of leaked memory ==20487== ==20487== For counts of detected and suppressed errors, rerun with: -v ==20487== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 1 from 1)