==23607== Memcheck, a memory error detector
==23607== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al.
==23607== Using Valgrind-3.10.0 and LibVEX; rerun with -h for copyright info
==23607== Command: binutils-gdb/binutils/objdump -x 078-47621-0.001:0.1
==23607== Parent PID: 17769
==23607== 
==23607== Invalid write of size 4
==23607==    at 0x4447EC: _bfd_coff_read_string_table (coffgen.c:1698)
==23607==    by 0x445157: _bfd_coff_internal_syment_name (coffgen.c:462)
==23607==    by 0x4A1027: handle_COMDAT (coffcode.h:960)
==23607==    by 0x4A1027: styp_to_sec_flags (coffcode.h:1285)
==23607==    by 0x444B24: make_a_section_from_file (coffgen.c:129)
==23607==    by 0x444B24: coff_real_object_p (coffgen.c:293)
==23607==    by 0x4A18BE: pe_bfd_object_p (peicode.h:1348)
==23607==    by 0x4468A6: bfd_check_format_matches (format.c:305)
==23607==    by 0x407EE1: display_object_bfd (objdump.c:3320)
==23607==    by 0x407EE1: display_any_bfd (objdump.c:3396)
==23607==    by 0x409FD2: display_file (objdump.c:3417)
==23607==    by 0x4048F9: main (objdump.c:3699)
==23607==  Address 0x0 is not stack'd, malloc'd or (recently) free'd
==23607== 
==23607== 
==23607== Process terminating with default action of signal 11 (SIGSEGV)
==23607==  Access not within mapped region at address 0x0
==23607==    at 0x4447EC: _bfd_coff_read_string_table (coffgen.c:1698)
==23607==    by 0x445157: _bfd_coff_internal_syment_name (coffgen.c:462)
==23607==    by 0x4A1027: handle_COMDAT (coffcode.h:960)
==23607==    by 0x4A1027: styp_to_sec_flags (coffcode.h:1285)
==23607==    by 0x444B24: make_a_section_from_file (coffgen.c:129)
==23607==    by 0x444B24: coff_real_object_p (coffgen.c:293)
==23607==    by 0x4A18BE: pe_bfd_object_p (peicode.h:1348)
==23607==    by 0x4468A6: bfd_check_format_matches (format.c:305)
==23607==    by 0x407EE1: display_object_bfd (objdump.c:3320)
==23607==    by 0x407EE1: display_any_bfd (objdump.c:3396)
==23607==    by 0x409FD2: display_file (objdump.c:3417)
==23607==    by 0x4048F9: main (objdump.c:3699)
==23607==  If you believe this happened as a result of a stack
==23607==  overflow in your program's main thread (unlikely but
==23607==  possible), you can try to increase the size of the
==23607==  main thread stack using the --main-stacksize= flag.
==23607==  The main thread stack size used in this run was 8388608.
==23607== 
==23607== HEAP SUMMARY:
==23607==     in use at exit: 17,664 bytes in 9 blocks
==23607==   total heap usage: 12 allocs, 3 frees, 17,730 bytes allocated
==23607== 
==23607== LEAK SUMMARY:
==23607==    definitely lost: 0 bytes in 0 blocks
==23607==    indirectly lost: 0 bytes in 0 blocks
==23607==      possibly lost: 0 bytes in 0 blocks
==23607==    still reachable: 17,664 bytes in 9 blocks
==23607==         suppressed: 0 bytes in 0 blocks
==23607== Rerun with --leak-check=full to see details of leaked memory
==23607== 
==23607== For counts of detected and suppressed errors, rerun with: -v
==23607== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 1 from 1)