==2074== Memcheck, a memory error detector
==2074== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al.
==2074== Using Valgrind-3.10.0 and LibVEX; rerun with -h for copyright info
==2074== Command: binutils-gdb/binutils/objdump -afphxgGtTrRwW --special-syms 078-1691-0.005
==2074== Parent PID: 6172
==2074== 
==2074== Invalid write of size 4
==2074==    at 0x444DCC: _bfd_coff_read_string_table (coffgen.c:1718)
==2074==    by 0x445DB3: coff_get_normalized_symtab (coffgen.c:1917)
==2074==    by 0x4A0965: coff_slurp_symbol_table.part.6 (coffcode.h:4705)
==2074==    by 0x4438C4: coff_get_symtab_upper_bound (coffgen.c:409)
==2074==    by 0x4073EE: slurp_symtab (objdump.c:563)
==2074==    by 0x4073EE: dump_bfd (objdump.c:3242)
==2074==    by 0x407F3F: display_object_bfd (objdump.c:3330)
==2074==    by 0x407F3F: display_any_bfd (objdump.c:3404)
==2074==    by 0x40A002: display_file (objdump.c:3425)
==2074==    by 0x4048F9: main (objdump.c:3707)
==2074==  Address 0x0 is not stack'd, malloc'd or (recently) free'd
==2074== 
==2074== 
==2074== Process terminating with default action of signal 11 (SIGSEGV)
==2074==  Access not within mapped region at address 0x0
==2074==    at 0x444DCC: _bfd_coff_read_string_table (coffgen.c:1718)
==2074==    by 0x445DB3: coff_get_normalized_symtab (coffgen.c:1917)
==2074==    by 0x4A0965: coff_slurp_symbol_table.part.6 (coffcode.h:4705)
==2074==    by 0x4438C4: coff_get_symtab_upper_bound (coffgen.c:409)
==2074==    by 0x4073EE: slurp_symtab (objdump.c:563)
==2074==    by 0x4073EE: dump_bfd (objdump.c:3242)
==2074==    by 0x407F3F: display_object_bfd (objdump.c:3330)
==2074==    by 0x407F3F: display_any_bfd (objdump.c:3404)
==2074==    by 0x40A002: display_file (objdump.c:3425)
==2074==    by 0x4048F9: main (objdump.c:3707)
==2074==  If you believe this happened as a result of a stack
==2074==  overflow in your program's main thread (unlikely but
==2074==  possible), you can try to increase the size of the
==2074==  main thread stack using the --main-stacksize= flag.
==2074==  The main thread stack size used in this run was 8388608.
==2074== 
==2074== HEAP SUMMARY:
==2074==     in use at exit: 40,703 bytes in 12 blocks
==2074==   total heap usage: 33 allocs, 21 frees, 88,300 bytes allocated
==2074== 
==2074== LEAK SUMMARY:
==2074==    definitely lost: 0 bytes in 0 blocks
==2074==    indirectly lost: 0 bytes in 0 blocks
==2074==      possibly lost: 0 bytes in 0 blocks
==2074==    still reachable: 40,703 bytes in 12 blocks
==2074==         suppressed: 0 bytes in 0 blocks
==2074== Rerun with --leak-check=full to see details of leaked memory
==2074== 
==2074== For counts of detected and suppressed errors, rerun with: -v
==2074== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 1 from 1)