==25478== Memcheck, a memory error detector ==25478== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al. ==25478== Using Valgrind-3.10.0 and LibVEX; rerun with -h for copyright info ==25478== Command: binutils-gdb/binutils/objdump -afphxgGtTrRwW --special-syms 10450-2643-0.004 ==25478== Parent PID: 1629 ==25478== ==25478== Invalid write of size 2 ==25478== at 0x41D72D: display_debug_frames (dwarf.c:5883) ==25478== by 0x40FA8C: dump_dwarf_section (objdump.c:2368) ==25478== by 0x50188B: bfd_map_over_sections (section.c:1354) ==25478== by 0x40B593: dump_dwarf (objdump.c:2426) ==25478== by 0x40CE64: dump_bfd (objdump.c:3263) ==25478== by 0x40D6EF: display_object_bfd (objdump.c:3330) ==25478== by 0x40D6EF: display_any_bfd (objdump.c:3404) ==25478== by 0x40F7B2: display_file (objdump.c:3425) ==25478== by 0x40A079: main (objdump.c:3707) ==25478== Address 0x2056410de is not stack'd, malloc'd or (recently) free'd ==25478== ==25478== ==25478== Process terminating with default action of signal 11 (SIGSEGV) ==25478== Access not within mapped region at address 0x2056410DE ==25478== at 0x41D72D: display_debug_frames (dwarf.c:5883) ==25478== by 0x40FA8C: dump_dwarf_section (objdump.c:2368) ==25478== by 0x50188B: bfd_map_over_sections (section.c:1354) ==25478== by 0x40B593: dump_dwarf (objdump.c:2426) ==25478== by 0x40CE64: dump_bfd (objdump.c:3263) ==25478== by 0x40D6EF: display_object_bfd (objdump.c:3330) ==25478== by 0x40D6EF: display_any_bfd (objdump.c:3404) ==25478== by 0x40F7B2: display_file (objdump.c:3425) ==25478== by 0x40A079: main (objdump.c:3707) ==25478== If you believe this happened as a result of a stack ==25478== overflow in your program's main thread (unlikely but ==25478== possible), you can try to increase the size of the ==25478== main thread stack using the --main-stacksize= flag. ==25478== The main thread stack size used in this run was 8388608. ==25478== ==25478== HEAP SUMMARY: ==25478== in use at exit: 60,411 bytes in 25 blocks ==25478== total heap usage: 99 allocs, 74 frees, 288,185 bytes allocated ==25478== ==25478== LEAK SUMMARY: ==25478== definitely lost: 0 bytes in 0 blocks ==25478== indirectly lost: 0 bytes in 0 blocks ==25478== possibly lost: 0 bytes in 0 blocks ==25478== still reachable: 60,411 bytes in 25 blocks ==25478== suppressed: 0 bytes in 0 blocks ==25478== Rerun with --leak-check=full to see details of leaked memory ==25478== ==25478== For counts of detected and suppressed errors, rerun with: -v ==25478== ERROR SUMMARY: 2 errors from 1 contexts (suppressed: 1 from 1)