==31553== Memcheck, a memory error detector
==31553== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al.
==31553== Using Valgrind-3.10.0 and LibVEX; rerun with -h for copyright info
==31553== Command: binutils-gdb/binutils/objdump -afphxgGtTrRwW --special-syms 017-5167-0.004
==31553== Parent PID: 7579
==31553== 
==31553== Invalid read of size 8
==31553==    at 0x7C9949: ieee_slurp_sections (ieee.c:1228)
==31553==    by 0x7C9949: ieee_object_p (ieee.c:1951)
==31553==    by 0x4FE6A6: bfd_check_format_matches (format.c:305)
==31553==    by 0x40D6B1: display_object_bfd (objdump.c:3328)
==31553==    by 0x40D6B1: display_any_bfd (objdump.c:3404)
==31553==    by 0x40F7B2: display_file (objdump.c:3425)
==31553==    by 0x40A079: main (objdump.c:3707)
==31553==  Address 0x55fe2d0 is 816 bytes inside an unallocated block of size 4,173,888 in arena "client"
==31553== 
==31553== Invalid write of size 8
==31553==    at 0x7C995C: ieee_slurp_sections (ieee.c:1229)
==31553==    by 0x7C995C: ieee_object_p (ieee.c:1951)
==31553==    by 0x4FE6A6: bfd_check_format_matches (format.c:305)
==31553==    by 0x40D6B1: display_object_bfd (objdump.c:3328)
==31553==    by 0x40D6B1: display_any_bfd (objdump.c:3404)
==31553==    by 0x40F7B2: display_file (objdump.c:3425)
==31553==    by 0x40A079: main (objdump.c:3707)
==31553==  Address 0x38 is not stack'd, malloc'd or (recently) free'd
==31553== 
==31553== 
==31553== Process terminating with default action of signal 11 (SIGSEGV)
==31553==  Access not within mapped region at address 0x38
==31553==    at 0x7C995C: ieee_slurp_sections (ieee.c:1229)
==31553==    by 0x7C995C: ieee_object_p (ieee.c:1951)
==31553==    by 0x4FE6A6: bfd_check_format_matches (format.c:305)
==31553==    by 0x40D6B1: display_object_bfd (objdump.c:3328)
==31553==    by 0x40D6B1: display_any_bfd (objdump.c:3404)
==31553==    by 0x40F7B2: display_file (objdump.c:3425)
==31553==    by 0x40A079: main (objdump.c:3707)
==31553==  If you believe this happened as a result of a stack
==31553==  overflow in your program's main thread (unlikely but
==31553==  possible), you can try to increase the size of the
==31553==  main thread stack using the --main-stacksize= flag.
==31553==  The main thread stack size used in this run was 8388608.
==31553== 
==31553== HEAP SUMMARY:
==31553==     in use at exit: 14,127 bytes in 9 blocks
==31553==   total heap usage: 15 allocs, 6 frees, 19,279 bytes allocated
==31553== 
==31553== LEAK SUMMARY:
==31553==    definitely lost: 0 bytes in 0 blocks
==31553==    indirectly lost: 0 bytes in 0 blocks
==31553==      possibly lost: 0 bytes in 0 blocks
==31553==    still reachable: 14,127 bytes in 9 blocks
==31553==         suppressed: 0 bytes in 0 blocks
==31553== Rerun with --leak-check=full to see details of leaked memory
==31553== 
==31553== For counts of detected and suppressed errors, rerun with: -v
==31553== ERROR SUMMARY: 2 errors from 2 contexts (suppressed: 1 from 1)