==11218== Memcheck, a memory error detector
==11218== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al.
==11218== Using Valgrind-3.10.0 and LibVEX; rerun with -h for copyright info
==11218== Command: binutils-gdb/binutils/objdump -afphxgGtTrRwW --special-syms samples/cd92277c
==11218== Parent PID: 11217
==11218== 
==11218== Warning: set address range perms: large range [0x59fd040, 0x35d00070) (undefined)
==11218== Invalid read of size 8
==11218==    at 0x83D902: versados_canonicalize_reloc (versados.c:801)
==11218==    by 0x40E37C: dump_relocs_in_section (objdump.c:3153)
==11218==    by 0x50019B: bfd_map_over_sections (section.c:1354)
==11218==    by 0x40D59D: dump_relocs (objdump.c:3175)
==11218==    by 0x40D59D: dump_bfd (objdump.c:3301)
==11218==    by 0x40DF27: display_object_bfd (objdump.c:3364)
==11218==    by 0x40DF27: display_any_bfd (objdump.c:3446)
==11218==    by 0x40FEA2: display_file (objdump.c:3467)
==11218==    by 0x40A849: main (objdump.c:3749)
==11218==  Address 0x100 is not stack'd, malloc'd or (recently) free'd
==11218== 
==11218== 
==11218== Process terminating with default action of signal 11 (SIGSEGV)
==11218==  Access not within mapped region at address 0x100
==11218==    at 0x83D902: versados_canonicalize_reloc (versados.c:801)
==11218==    by 0x40E37C: dump_relocs_in_section (objdump.c:3153)
==11218==    by 0x50019B: bfd_map_over_sections (section.c:1354)
==11218==    by 0x40D59D: dump_relocs (objdump.c:3175)
==11218==    by 0x40D59D: dump_bfd (objdump.c:3301)
==11218==    by 0x40DF27: display_object_bfd (objdump.c:3364)
==11218==    by 0x40DF27: display_any_bfd (objdump.c:3446)
==11218==    by 0x40FEA2: display_file (objdump.c:3467)
==11218==    by 0x40A849: main (objdump.c:3749)
==11218==  If you believe this happened as a result of a stack
==11218==  overflow in your program's main thread (unlikely but
==11218==  possible), you can try to increase the size of the
==11218==  main thread stack using the --main-stacksize= flag.
==11218==  The main thread stack size used in this run was 8388608.
==11218== 
==11218== HEAP SUMMARY:
==11218==     in use at exit: 808,473,737 bytes in 57 blocks
==11218==   total heap usage: 68 allocs, 11 frees, 808,523,071 bytes allocated
==11218== 
==11218== LEAK SUMMARY:
==11218==    definitely lost: 79 bytes in 37 blocks
==11218==    indirectly lost: 0 bytes in 0 blocks
==11218==      possibly lost: 0 bytes in 0 blocks
==11218==    still reachable: 808,473,658 bytes in 20 blocks
==11218==         suppressed: 0 bytes in 0 blocks
==11218== Rerun with --leak-check=full to see details of leaked memory
==11218== 
==11218== For counts of detected and suppressed errors, rerun with: -v
==11218== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)