==10077== Memcheck, a memory error detector
==10077== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al.
==10077== Using Valgrind-3.10.0 and LibVEX; rerun with -h for copyright info
==10077== Command: binutils-gdb/binutils/objdump -afphxgGtTrRwW --special-syms samples/ac7da425
==10077== Parent PID: 10076
==10077== 
==10077== Invalid read of size 8
==10077==    at 0x83CD44: process_otr (versados.c:464)
==10077==    by 0x83D744: versados_scan (versados.c:504)
==10077==    by 0x83D744: versados_object_p (versados.c:631)
==10077==    by 0x4FC704: bfd_check_format_matches (format.c:305)
==10077==    by 0x40DEE9: display_object_bfd (objdump.c:3362)
==10077==    by 0x40DEE9: display_any_bfd (objdump.c:3446)
==10077==    by 0x40FEA2: display_file (objdump.c:3467)
==10077==    by 0x40A849: main (objdump.c:3749)
==10077==  Address 0x3b is not stack'd, malloc'd or (recently) free'd
==10077== 
==10077== 
==10077== Process terminating with default action of signal 11 (SIGSEGV)
==10077==  Access not within mapped region at address 0x3B
==10077==    at 0x83CD44: process_otr (versados.c:464)
==10077==    by 0x83D744: versados_scan (versados.c:504)
==10077==    by 0x83D744: versados_object_p (versados.c:631)
==10077==    by 0x4FC704: bfd_check_format_matches (format.c:305)
==10077==    by 0x40DEE9: display_object_bfd (objdump.c:3362)
==10077==    by 0x40DEE9: display_any_bfd (objdump.c:3446)
==10077==    by 0x40FEA2: display_file (objdump.c:3467)
==10077==    by 0x40A849: main (objdump.c:3749)
==10077==  If you believe this happened as a result of a stack
==10077==  overflow in your program's main thread (unlikely but
==10077==  possible), you can try to increase the size of the
==10077==  main thread stack using the --main-stacksize= flag.
==10077==  The main thread stack size used in this run was 8388608.
==10077== 
==10077== HEAP SUMMARY:
==10077==     in use at exit: 14,072 bytes in 25 blocks
==10077==   total heap usage: 28 allocs, 3 frees, 19,174 bytes allocated
==10077== 
==10077== LEAK SUMMARY:
==10077==    definitely lost: 20 bytes in 10 blocks
==10077==    indirectly lost: 0 bytes in 0 blocks
==10077==      possibly lost: 0 bytes in 0 blocks
==10077==    still reachable: 14,052 bytes in 15 blocks
==10077==         suppressed: 0 bytes in 0 blocks
==10077== Rerun with --leak-check=full to see details of leaked memory
==10077== 
==10077== For counts of detected and suppressed errors, rerun with: -v
==10077== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)