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