==20183== Memcheck, a memory error detector ==20183== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al. ==20183== Using Valgrind-3.10.0 and LibVEX; rerun with -h for copyright info ==20183== Command: binutils-gdb/binutils/objdump -afphxgGtTrRwW --special-syms 069-133014-0.006 ==20183== Parent PID: 10205 ==20183== ==20183== Invalid read of size 1 ==20183== at 0x40CC1D: decode_location_expression (dwarf.c:872) ==20183== by 0x418C50: display_debug_frames (dwarf.c:6128) ==20183== by 0x40A2DC: dump_dwarf_section (objdump.c:2368) ==20183== by 0x44A07B: bfd_map_over_sections (section.c:1354) ==20183== by 0x405DF3: dump_dwarf (objdump.c:2426) ==20183== by 0x40774B: dump_bfd (objdump.c:3263) ==20183== by 0x407F3F: display_object_bfd (objdump.c:3330) ==20183== by 0x407F3F: display_any_bfd (objdump.c:3404) ==20183== by 0x40A002: display_file (objdump.c:3425) ==20183== by 0x4048F9: main (objdump.c:3707) ==20183== Address 0x5626800 is 0 bytes after a block of size 512 alloc'd ==20183== at 0x4C27C20: malloc (vg_replace_malloc.c:296) ==20183== by 0x44783D: bfd_malloc (libbfd.c:181) ==20183== by 0x458737: bfd_get_full_section_contents (compress.c:182) ==20183== by 0x40A0E1: load_specific_debug_section (objdump.c:2268) ==20183== by 0x40A2C4: dump_dwarf_section (objdump.c:2365) ==20183== by 0x44A07B: bfd_map_over_sections (section.c:1354) ==20183== by 0x405DF3: dump_dwarf (objdump.c:2426) ==20183== by 0x40774B: dump_bfd (objdump.c:3263) ==20183== by 0x407F3F: display_object_bfd (objdump.c:3330) ==20183== by 0x407F3F: display_any_bfd (objdump.c:3404) ==20183== by 0x40A002: display_file (objdump.c:3425) ==20183== by 0x4048F9: main (objdump.c:3707) ==20183== ==20183== Warning: set address range perms: large range [0x95fd040, 0x195fd060) (undefined) ==20183== Warning: set address range perms: large range [0x95fd028, 0x195fd078) (noaccess) ==20183== ==20183== HEAP SUMMARY: ==20183== in use at exit: 1,300,649 bytes in 217 blocks ==20183== total heap usage: 663 allocs, 446 frees, 496,195,642 bytes allocated ==20183== ==20183== LEAK SUMMARY: ==20183== definitely lost: 30,808 bytes in 161 blocks ==20183== indirectly lost: 384 bytes in 2 blocks ==20183== possibly lost: 0 bytes in 0 blocks ==20183== still reachable: 1,269,457 bytes in 54 blocks ==20183== suppressed: 0 bytes in 0 blocks ==20183== Rerun with --leak-check=full to see details of leaked memory ==20183== ==20183== For counts of detected and suppressed errors, rerun with: -v ==20183== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 1 from 1)