==30277== Memcheck, a memory error detector ==30277== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al. ==30277== Using Valgrind-3.10.0 and LibVEX; rerun with -h for copyright info ==30277== Command: binutils-gdb/binutils/objdump -afphxgGWtTrRw --special-syms 337-185408-0.004 ==30277== Parent PID: 29198 ==30277== ==30277== Invalid write of size 4 ==30277== at 0x444BDC: _bfd_coff_read_string_table (coffgen.c:1698) ==30277== by 0x445547: _bfd_coff_internal_syment_name (coffgen.c:462) ==30277== by 0x4A4D2D: _bfd_pei_swap_sym_in (peigen.c:150) ==30277== by 0x4456A0: coff_get_normalized_symtab (coffgen.c:1786) ==30277== by 0x4A0435: coff_slurp_symbol_table.part.5 (coffcode.h:4685) ==30277== by 0x4437F4: coff_get_symtab_upper_bound (coffgen.c:409) ==30277== by 0x4073EE: slurp_symtab (objdump.c:563) ==30277== by 0x4073EE: dump_bfd (objdump.c:3242) ==30277== by 0x407F3F: display_object_bfd (objdump.c:3330) ==30277== by 0x407F3F: display_any_bfd (objdump.c:3404) ==30277== by 0x40A002: display_file (objdump.c:3425) ==30277== by 0x4048F9: main (objdump.c:3707) ==30277== Address 0x0 is not stack'd, malloc'd or (recently) free'd ==30277== ==30277== ==30277== Process terminating with default action of signal 11 (SIGSEGV) ==30277== Access not within mapped region at address 0x0 ==30277== at 0x444BDC: _bfd_coff_read_string_table (coffgen.c:1698) ==30277== by 0x445547: _bfd_coff_internal_syment_name (coffgen.c:462) ==30277== by 0x4A4D2D: _bfd_pei_swap_sym_in (peigen.c:150) ==30277== by 0x4456A0: coff_get_normalized_symtab (coffgen.c:1786) ==30277== by 0x4A0435: coff_slurp_symbol_table.part.5 (coffcode.h:4685) ==30277== by 0x4437F4: coff_get_symtab_upper_bound (coffgen.c:409) ==30277== by 0x4073EE: slurp_symtab (objdump.c:563) ==30277== by 0x4073EE: dump_bfd (objdump.c:3242) ==30277== by 0x407F3F: display_object_bfd (objdump.c:3330) ==30277== by 0x407F3F: display_any_bfd (objdump.c:3404) ==30277== by 0x40A002: display_file (objdump.c:3425) ==30277== by 0x4048F9: main (objdump.c:3707) ==30277== If you believe this happened as a result of a stack ==30277== overflow in your program's main thread (unlikely but ==30277== possible), you can try to increase the size of the ==30277== main thread stack using the --main-stacksize= flag. ==30277== The main thread stack size used in this run was 8388608. ==30277== ==30277== HEAP SUMMARY: ==30277== in use at exit: 4,413,126 bytes in 10 blocks ==30277== total heap usage: 31 allocs, 21 frees, 4,849,208 bytes allocated ==30277== ==30277== LEAK SUMMARY: ==30277== definitely lost: 78,709 bytes in 1 blocks ==30277== indirectly lost: 0 bytes in 0 blocks ==30277== possibly lost: 0 bytes in 0 blocks ==30277== still reachable: 4,334,417 bytes in 9 blocks ==30277== suppressed: 0 bytes in 0 blocks ==30277== Rerun with --leak-check=full to see details of leaked memory ==30277== ==30277== For counts of detected and suppressed errors, rerun with: -v ==30277== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 1 from 1)