==26444== Memcheck, a memory error detector
==26444== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al.
==26444== Using Valgrind-3.10.0 and LibVEX; rerun with -h for copyright info
==26444== Command: binutils-gdb/binutils/objdump -afphxgGtTrRwW --special-syms samples/fe3b9a79
==26444== Parent PID: 22957
==26444== 
==26444== Invalid read of size 8
==26444==    at 0x4486E8: bfd_check_format_matches (format.c:411)
==26444==    by 0x40802D: display_any_bfd (objdump.c:3404)
==26444==    by 0x40A0C2: display_file (objdump.c:3466)
==26444==    by 0x404AB9: main (objdump.c:3748)
==26444==  Address 0x0 is not stack'd, malloc'd or (recently) free'd
==26444== 
==26444== 
==26444== Process terminating with default action of signal 11 (SIGSEGV)
==26444==  Access not within mapped region at address 0x0
==26444==    at 0x4486E8: bfd_check_format_matches (format.c:411)
==26444==    by 0x40802D: display_any_bfd (objdump.c:3404)
==26444==    by 0x40A0C2: display_file (objdump.c:3466)
==26444==    by 0x404AB9: main (objdump.c:3748)
==26444==  If you believe this happened as a result of a stack
==26444==  overflow in your program's main thread (unlikely but
==26444==  possible), you can try to increase the size of the
==26444==  main thread stack using the --main-stacksize= flag.
==26444==  The main thread stack size used in this run was 8388608.
==26444== 
==26444== HEAP SUMMARY:
==26444==     in use at exit: 189,892 bytes in 95 blocks
==26444==   total heap usage: 136 allocs, 41 frees, 415,509 bytes allocated
==26444== 
==26444== LEAK SUMMARY:
==26444==    definitely lost: 0 bytes in 0 blocks
==26444==    indirectly lost: 0 bytes in 0 blocks
==26444==      possibly lost: 0 bytes in 0 blocks
==26444==    still reachable: 189,892 bytes in 95 blocks
==26444==         suppressed: 0 bytes in 0 blocks
==26444== Rerun with --leak-check=full to see details of leaked memory
==26444== 
==26444== For counts of detected and suppressed errors, rerun with: -v
==26444== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)