==6250== Memcheck, a memory error detector
==6250== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al.
==6250== Using Valgrind-3.10.0 and LibVEX; rerun with -h for copyright info
==6250== Command: binutils-gdb/binutils/objdump -afphxgGtTrRwW --special-syms 091-1180-0.004
==6250== Parent PID: 31739
==6250== 
==6250== Invalid read of size 8
==6250==    at 0x7C68BE: ieee_slurp_section_data (ieee.c:1700)
==6250==    by 0x7C9776: ieee_object_p (ieee.c:1958)
==6250==    by 0x4FE6A6: bfd_check_format_matches (format.c:305)
==6250==    by 0x40D6B1: display_object_bfd (objdump.c:3328)
==6250==    by 0x40D6B1: display_any_bfd (objdump.c:3404)
==6250==    by 0x40F7B2: display_file (objdump.c:3425)
==6250==    by 0x40A079: main (objdump.c:3707)
==6250==  Address 0xe0 is not stack'd, malloc'd or (recently) free'd
==6250== 
==6250== 
==6250== Process terminating with default action of signal 11 (SIGSEGV)
==6250==  Access not within mapped region at address 0xE0
==6250==    at 0x7C68BE: ieee_slurp_section_data (ieee.c:1700)
==6250==    by 0x7C9776: ieee_object_p (ieee.c:1958)
==6250==    by 0x4FE6A6: bfd_check_format_matches (format.c:305)
==6250==    by 0x40D6B1: display_object_bfd (objdump.c:3328)
==6250==    by 0x40D6B1: display_any_bfd (objdump.c:3404)
==6250==    by 0x40F7B2: display_file (objdump.c:3425)
==6250==    by 0x40A079: main (objdump.c:3707)
==6250==  If you believe this happened as a result of a stack
==6250==  overflow in your program's main thread (unlikely but
==6250==  possible), you can try to increase the size of the
==6250==  main thread stack using the --main-stacksize= flag.
==6250==  The main thread stack size used in this run was 8388608.
==6250== 
==6250== HEAP SUMMARY:
==6250==     in use at exit: 32,909,159 bytes in 10 blocks
==6250==   total heap usage: 16 allocs, 6 frees, 32,914,311 bytes allocated
==6250== 
==6250== LEAK SUMMARY:
==6250==    definitely lost: 0 bytes in 0 blocks
==6250==    indirectly lost: 0 bytes in 0 blocks
==6250==      possibly lost: 0 bytes in 0 blocks
==6250==    still reachable: 32,909,159 bytes in 10 blocks
==6250==         suppressed: 0 bytes in 0 blocks
==6250== Rerun with --leak-check=full to see details of leaked memory
==6250== 
==6250== For counts of detected and suppressed errors, rerun with: -v
==6250== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 1 from 1)