==16761== Memcheck, a memory error detector
==16761== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al.
==16761== Using Valgrind-3.10.0 and LibVEX; rerun with -h for copyright info
==16761== Command: binutils-gdb/binutils/objdump -afphxgGtTrRwW --special-syms 002-10114-0.004
==16761== Parent PID: 2719
==16761== 
==16761== Invalid read of size 1
==16761==    at 0x40FFEA: process_extended_line_op (dwarf.c:553)
==16761==    by 0x40FFEA: display_debug_lines_raw (dwarf.c:2896)
==16761==    by 0x40FFEA: display_debug_lines (dwarf.c:3515)
==16761==    by 0x40A2DC: dump_dwarf_section (objdump.c:2368)
==16761==    by 0x44A07B: bfd_map_over_sections (section.c:1354)
==16761==    by 0x405DF3: dump_dwarf (objdump.c:2426)
==16761==    by 0x40774B: dump_bfd (objdump.c:3263)
==16761==    by 0x407F3F: display_object_bfd (objdump.c:3330)
==16761==    by 0x407F3F: display_any_bfd (objdump.c:3404)
==16761==    by 0x40A002: display_file (objdump.c:3425)
==16761==    by 0x4048F9: main (objdump.c:3707)
==16761==  Address 0x563946f is 0 bytes after a block of size 607 alloc'd
==16761==    at 0x4C27C20: malloc (vg_replace_malloc.c:296)
==16761==    by 0x44783D: bfd_malloc (libbfd.c:181)
==16761==    by 0x458737: bfd_get_full_section_contents (compress.c:182)
==16761==    by 0x40A0E1: load_specific_debug_section (objdump.c:2268)
==16761==    by 0x40A2C4: dump_dwarf_section (objdump.c:2365)
==16761==    by 0x44A07B: bfd_map_over_sections (section.c:1354)
==16761==    by 0x405DF3: dump_dwarf (objdump.c:2426)
==16761==    by 0x40774B: dump_bfd (objdump.c:3263)
==16761==    by 0x407F3F: display_object_bfd (objdump.c:3330)
==16761==    by 0x407F3F: display_any_bfd (objdump.c:3404)
==16761==    by 0x40A002: display_file (objdump.c:3425)
==16761==    by 0x4048F9: main (objdump.c:3707)
==16761== 
==16761== 
==16761== Process terminating with default action of signal 11 (SIGSEGV)
==16761==  Access not within mapped region at address 0x59F9000
==16761==    at 0x40FFEA: process_extended_line_op (dwarf.c:553)
==16761==    by 0x40FFEA: display_debug_lines_raw (dwarf.c:2896)
==16761==    by 0x40FFEA: display_debug_lines (dwarf.c:3515)
==16761==    by 0x40A2DC: dump_dwarf_section (objdump.c:2368)
==16761==    by 0x44A07B: bfd_map_over_sections (section.c:1354)
==16761==    by 0x405DF3: dump_dwarf (objdump.c:2426)
==16761==    by 0x40774B: dump_bfd (objdump.c:3263)
==16761==    by 0x407F3F: display_object_bfd (objdump.c:3330)
==16761==    by 0x407F3F: display_any_bfd (objdump.c:3404)
==16761==    by 0x40A002: display_file (objdump.c:3425)
==16761==    by 0x4048F9: main (objdump.c:3707)
==16761==  If you believe this happened as a result of a stack
==16761==  overflow in your program's main thread (unlikely but
==16761==  possible), you can try to increase the size of the
==16761==  main thread stack using the --main-stacksize= flag.
==16761==  The main thread stack size used in this run was 8388608.
==16761== 
==16761== HEAP SUMMARY:
==16761==     in use at exit: 166,903 bytes in 22 blocks
==16761==   total heap usage: 56 allocs, 34 frees, 115,603,170 bytes allocated
==16761== 
==16761== LEAK SUMMARY:
==16761==    definitely lost: 0 bytes in 0 blocks
==16761==    indirectly lost: 0 bytes in 0 blocks
==16761==      possibly lost: 0 bytes in 0 blocks
==16761==    still reachable: 166,903 bytes in 22 blocks
==16761==         suppressed: 0 bytes in 0 blocks
==16761== Rerun with --leak-check=full to see details of leaked memory
==16761== 
==16761== For counts of detected and suppressed errors, rerun with: -v
==16761== ERROR SUMMARY: 3931026 errors from 1 contexts (suppressed: 1 from 1)