==21583== Memcheck, a memory error detector ==21583== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al. ==21583== Using Valgrind-3.10.0 and LibVEX; rerun with -h for copyright info ==21583== Command: binutils-gdb/binutils/objdump -afphxgGtTrRwW --special-syms 002-155137-0.004 ==21583== Parent PID: 10778 ==21583== ==21583== Invalid write of size 4 ==21583== at 0x444C0C: _bfd_coff_read_string_table (coffgen.c:1718) ==21583== by 0x445577: _bfd_coff_internal_syment_name (coffgen.c:462) ==21583== by 0x4A1877: handle_COMDAT (coffcode.h:963) ==21583== by 0x4A1877: styp_to_sec_flags (coffcode.h:1288) ==21583== by 0x444F44: make_a_section_from_file (coffgen.c:129) ==21583== by 0x444F44: coff_real_object_p (coffgen.c:293) ==21583== by 0x4A210E: pe_bfd_object_p (peicode.h:1349) ==21583== by 0x446FA6: bfd_check_format_matches (format.c:305) ==21583== by 0x407F01: display_object_bfd (objdump.c:3328) ==21583== by 0x407F01: display_any_bfd (objdump.c:3404) ==21583== by 0x40A002: display_file (objdump.c:3425) ==21583== by 0x4048F9: main (objdump.c:3707) ==21583== Address 0x0 is not stack'd, malloc'd or (recently) free'd ==21583== ==21583== ==21583== Process terminating with default action of signal 11 (SIGSEGV) ==21583== Access not within mapped region at address 0x0 ==21583== at 0x444C0C: _bfd_coff_read_string_table (coffgen.c:1718) ==21583== by 0x445577: _bfd_coff_internal_syment_name (coffgen.c:462) ==21583== by 0x4A1877: handle_COMDAT (coffcode.h:963) ==21583== by 0x4A1877: styp_to_sec_flags (coffcode.h:1288) ==21583== by 0x444F44: make_a_section_from_file (coffgen.c:129) ==21583== by 0x444F44: coff_real_object_p (coffgen.c:293) ==21583== by 0x4A210E: pe_bfd_object_p (peicode.h:1349) ==21583== by 0x446FA6: bfd_check_format_matches (format.c:305) ==21583== by 0x407F01: display_object_bfd (objdump.c:3328) ==21583== by 0x407F01: display_any_bfd (objdump.c:3404) ==21583== by 0x40A002: display_file (objdump.c:3425) ==21583== by 0x4048F9: main (objdump.c:3707) ==21583== If you believe this happened as a result of a stack ==21583== overflow in your program's main thread (unlikely but ==21583== possible), you can try to increase the size of the ==21583== main thread stack using the --main-stacksize= flag. ==21583== The main thread stack size used in this run was 8388608. ==21583== ==21583== HEAP SUMMARY: ==21583== in use at exit: 21,999 bytes in 9 blocks ==21583== total heap usage: 12 allocs, 3 frees, 22,065 bytes allocated ==21583== ==21583== LEAK SUMMARY: ==21583== definitely lost: 0 bytes in 0 blocks ==21583== indirectly lost: 0 bytes in 0 blocks ==21583== possibly lost: 0 bytes in 0 blocks ==21583== still reachable: 21,999 bytes in 9 blocks ==21583== suppressed: 0 bytes in 0 blocks ==21583== Rerun with --leak-check=full to see details of leaked memory ==21583== ==21583== For counts of detected and suppressed errors, rerun with: -v ==21583== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 1 from 1)