==3704== Memcheck, a memory error detector
==3704== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al.
==3704== Using Valgrind-3.10.0 and LibVEX; rerun with -h for copyright info
==3704== Command: binutils-gdb/binutils/objdump -afphxgGtTrRwW --special-syms 005-181405-0.004
==3704== Parent PID: 11455
==3704== 
==3704== Invalid read of size 1
==3704==    at 0x447C00: bfd_getl32 (libbfd.c:620)
==3704==    by 0x4B1925: pex64_get_runtime_function.isra.2 (pei-x86_64.c:94)
==3704==    by 0x4B1BFF: pex64_bfd_print_pdata (pei-x86_64.c:493)
==3704==    by 0x4BA386: _bfd_pex64_print_private_bfd_data_common (pex64igen.c:2849)
==3704==    by 0x4B43F8: pe_print_private_bfd_data (peicode.h:336)
==3704==    by 0x40790E: dump_bfd_private_header (objdump.c:2656)
==3704==    by 0x40790E: dump_bfd (objdump.c:3231)
==3704==    by 0x407F3F: display_object_bfd (objdump.c:3330)
==3704==    by 0x407F3F: display_any_bfd (objdump.c:3404)
==3704==    by 0x40A002: display_file (objdump.c:3425)
==3704==    by 0x4048F9: main (objdump.c:3707)
==3704==  Address 0x1 is not stack'd, malloc'd or (recently) free'd
==3704== 
==3704== 
==3704== Process terminating with default action of signal 11 (SIGSEGV)
==3704==  Access not within mapped region at address 0x1
==3704==    at 0x447C00: bfd_getl32 (libbfd.c:620)
==3704==    by 0x4B1925: pex64_get_runtime_function.isra.2 (pei-x86_64.c:94)
==3704==    by 0x4B1BFF: pex64_bfd_print_pdata (pei-x86_64.c:493)
==3704==    by 0x4BA386: _bfd_pex64_print_private_bfd_data_common (pex64igen.c:2849)
==3704==    by 0x4B43F8: pe_print_private_bfd_data (peicode.h:336)
==3704==    by 0x40790E: dump_bfd_private_header (objdump.c:2656)
==3704==    by 0x40790E: dump_bfd (objdump.c:3231)
==3704==    by 0x407F3F: display_object_bfd (objdump.c:3330)
==3704==    by 0x407F3F: display_any_bfd (objdump.c:3404)
==3704==    by 0x40A002: display_file (objdump.c:3425)
==3704==    by 0x4048F9: main (objdump.c:3707)
==3704==  If you believe this happened as a result of a stack
==3704==  overflow in your program's main thread (unlikely but
==3704==  possible), you can try to increase the size of the
==3704==  main thread stack using the --main-stacksize= flag.
==3704==  The main thread stack size used in this run was 8388608.
==3704== 
==3704== HEAP SUMMARY:
==3704==     in use at exit: 13,113 bytes in 9 blocks
==3704==   total heap usage: 28 allocs, 19 frees, 51,782 bytes allocated
==3704== 
==3704== LEAK SUMMARY:
==3704==    definitely lost: 0 bytes in 0 blocks
==3704==    indirectly lost: 0 bytes in 0 blocks
==3704==      possibly lost: 0 bytes in 0 blocks
==3704==    still reachable: 13,113 bytes in 9 blocks
==3704==         suppressed: 0 bytes in 0 blocks
==3704== Rerun with --leak-check=full to see details of leaked memory
==3704== 
==3704== For counts of detected and suppressed errors, rerun with: -v
==3704== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 1 from 1)