==9807== Memcheck, a memory error detector
==9807== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al.
==9807== Using Valgrind-3.10.0 and LibVEX; rerun with -h for copyright info
==9807== Command: binutils-gdb/binutils/objdump -afphxgGtTrRwW --special-syms samples/996185f8
==9807== Parent PID: 9806
==9807== 
==9807== Invalid read of size 8
==9807==    at 0x5E2244: elf64_sparc_slurp_one_reloc_table (elf64-sparc.c:107)
==9807==    by 0x5E2421: elf64_sparc_slurp_reloc_table (elf64-sparc.c:201)
==9807==    by 0x5E2005: elf64_sparc_canonicalize_reloc (elf64-sparc.c:218)
==9807==    by 0x40E37C: dump_relocs_in_section (objdump.c:3153)
==9807==    by 0x50019B: bfd_map_over_sections (section.c:1354)
==9807==    by 0x40D59D: dump_relocs (objdump.c:3175)
==9807==    by 0x40D59D: dump_bfd (objdump.c:3301)
==9807==    by 0x40DF27: display_object_bfd (objdump.c:3364)
==9807==    by 0x40DF27: display_any_bfd (objdump.c:3446)
==9807==    by 0x40FEA2: display_file (objdump.c:3467)
==9807==    by 0x40A849: main (objdump.c:3749)
==9807==  Address 0x105634e68 is not stack'd, malloc'd or (recently) free'd
==9807== 
==9807== 
==9807== Process terminating with default action of signal 11 (SIGSEGV)
==9807==  Access not within mapped region at address 0x105634E68
==9807==    at 0x5E2244: elf64_sparc_slurp_one_reloc_table (elf64-sparc.c:107)
==9807==    by 0x5E2421: elf64_sparc_slurp_reloc_table (elf64-sparc.c:201)
==9807==    by 0x5E2005: elf64_sparc_canonicalize_reloc (elf64-sparc.c:218)
==9807==    by 0x40E37C: dump_relocs_in_section (objdump.c:3153)
==9807==    by 0x50019B: bfd_map_over_sections (section.c:1354)
==9807==    by 0x40D59D: dump_relocs (objdump.c:3175)
==9807==    by 0x40D59D: dump_bfd (objdump.c:3301)
==9807==    by 0x40DF27: display_object_bfd (objdump.c:3364)
==9807==    by 0x40DF27: display_any_bfd (objdump.c:3446)
==9807==    by 0x40FEA2: display_file (objdump.c:3467)
==9807==    by 0x40A849: main (objdump.c:3749)
==9807==  If you believe this happened as a result of a stack
==9807==  overflow in your program's main thread (unlikely but
==9807==  possible), you can try to increase the size of the
==9807==  main thread stack using the --main-stacksize= flag.
==9807==  The main thread stack size used in this run was 8388608.
==9807== 
==9807== HEAP SUMMARY:
==9807==     in use at exit: 138,795 bytes in 44 blocks
==9807==   total heap usage: 135 allocs, 91 frees, 233,755 bytes allocated
==9807== 
==9807== LEAK SUMMARY:
==9807==    definitely lost: 144 bytes in 1 blocks
==9807==    indirectly lost: 0 bytes in 0 blocks
==9807==      possibly lost: 0 bytes in 0 blocks
==9807==    still reachable: 138,651 bytes in 43 blocks
==9807==         suppressed: 0 bytes in 0 blocks
==9807== Rerun with --leak-check=full to see details of leaked memory
==9807== 
==9807== For counts of detected and suppressed errors, rerun with: -v
==9807== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)