==8758== Memcheck, a memory error detector
==8758== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al.
==8758== Using Valgrind-3.10.0 and LibVEX; rerun with -h for copyright info
==8758== Command: binutils-gdb/binutils/objdump -x 078-63256-0.001:0.1
==8758== Parent PID: 17769
==8758== 
==8758== Invalid write of size 4
==8758==    at 0x4447EC: _bfd_coff_read_string_table (coffgen.c:1698)
==8758==    by 0x445157: _bfd_coff_internal_syment_name (coffgen.c:462)
==8758==    by 0x4A484D: _bfd_pei_swap_sym_in (peigen.c:150)
==8758==    by 0x4452B3: coff_get_normalized_symtab (coffgen.c:1786)
==8758==    by 0x49FFE5: coff_slurp_symbol_table.part.5 (coffcode.h:4671)
==8758==    by 0x443404: coff_get_symtab_upper_bound (coffgen.c:409)
==8758==    by 0x4073CE: slurp_symtab (objdump.c:563)
==8758==    by 0x4073CE: dump_bfd (objdump.c:3234)
==8758==    by 0x407F1F: display_object_bfd (objdump.c:3322)
==8758==    by 0x407F1F: display_any_bfd (objdump.c:3396)
==8758==    by 0x409FD2: display_file (objdump.c:3417)
==8758==    by 0x4048F9: main (objdump.c:3699)
==8758==  Address 0x0 is not stack'd, malloc'd or (recently) free'd
==8758== 
==8758== 
==8758== Process terminating with default action of signal 11 (SIGSEGV)
==8758==  Access not within mapped region at address 0x0
==8758==    at 0x4447EC: _bfd_coff_read_string_table (coffgen.c:1698)
==8758==    by 0x445157: _bfd_coff_internal_syment_name (coffgen.c:462)
==8758==    by 0x4A484D: _bfd_pei_swap_sym_in (peigen.c:150)
==8758==    by 0x4452B3: coff_get_normalized_symtab (coffgen.c:1786)
==8758==    by 0x49FFE5: coff_slurp_symbol_table.part.5 (coffcode.h:4671)
==8758==    by 0x443404: coff_get_symtab_upper_bound (coffgen.c:409)
==8758==    by 0x4073CE: slurp_symtab (objdump.c:563)
==8758==    by 0x4073CE: dump_bfd (objdump.c:3234)
==8758==    by 0x407F1F: display_object_bfd (objdump.c:3322)
==8758==    by 0x407F1F: display_any_bfd (objdump.c:3396)
==8758==    by 0x409FD2: display_file (objdump.c:3417)
==8758==    by 0x4048F9: main (objdump.c:3699)
==8758==  If you believe this happened as a result of a stack
==8758==  overflow in your program's main thread (unlikely but
==8758==  possible), you can try to increase the size of the
==8758==  main thread stack using the --main-stacksize= flag.
==8758==  The main thread stack size used in this run was 8388608.
==8758== 
==8758== HEAP SUMMARY:
==8758==     in use at exit: 43,600 bytes in 10 blocks
==8758==   total heap usage: 30 allocs, 20 frees, 253,924 bytes allocated
==8758== 
==8758== LEAK SUMMARY:
==8758==    definitely lost: 0 bytes in 0 blocks
==8758==    indirectly lost: 0 bytes in 0 blocks
==8758==      possibly lost: 0 bytes in 0 blocks
==8758==    still reachable: 43,600 bytes in 10 blocks
==8758==         suppressed: 0 bytes in 0 blocks
==8758== Rerun with --leak-check=full to see details of leaked memory
==8758== 
==8758== For counts of detected and suppressed errors, rerun with: -v
==8758== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 1 from 1)