==27871== Memcheck, a memory error detector
==27871== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al.
==27871== Using Valgrind-3.10.0 and LibVEX; rerun with -h for copyright info
==27871== Command: binutils-gdb/binutils/objdump -afphxgGtTrRwW --special-syms 130-9174-0.004
==27871== Parent PID: 8731
==27871== 
==27871== Invalid read of size 8
==27871==    at 0x83D30D: process_otr (versados.c:433)
==27871==    by 0x83DC74: versados_scan (versados.c:486)
==27871==    by 0x83DC74: versados_object_p (versados.c:607)
==27871==    by 0x4FE6A6: bfd_check_format_matches (format.c:305)
==27871==    by 0x40D6B1: display_object_bfd (objdump.c:3328)
==27871==    by 0x40D6B1: display_any_bfd (objdump.c:3404)
==27871==    by 0x40F7B2: display_file (objdump.c:3425)
==27871==    by 0x40A079: main (objdump.c:3707)
==27871==  Address 0x38 is not stack'd, malloc'd or (recently) free'd
==27871== 
==27871== 
==27871== Process terminating with default action of signal 11 (SIGSEGV)
==27871==  Access not within mapped region at address 0x38
==27871==    at 0x83D30D: process_otr (versados.c:433)
==27871==    by 0x83DC74: versados_scan (versados.c:486)
==27871==    by 0x83DC74: versados_object_p (versados.c:607)
==27871==    by 0x4FE6A6: bfd_check_format_matches (format.c:305)
==27871==    by 0x40D6B1: display_object_bfd (objdump.c:3328)
==27871==    by 0x40D6B1: display_any_bfd (objdump.c:3404)
==27871==    by 0x40F7B2: display_file (objdump.c:3425)
==27871==    by 0x40A079: main (objdump.c:3707)
==27871==  If you believe this happened as a result of a stack
==27871==  overflow in your program's main thread (unlikely but
==27871==  possible), you can try to increase the size of the
==27871==  main thread stack using the --main-stacksize= flag.
==27871==  The main thread stack size used in this run was 8388608.
==27871== 
==27871== HEAP SUMMARY:
==27871==     in use at exit: 13,967 bytes in 8 blocks
==27871==   total heap usage: 14 allocs, 6 frees, 19,119 bytes allocated
==27871== 
==27871== LEAK SUMMARY:
==27871==    definitely lost: 0 bytes in 0 blocks
==27871==    indirectly lost: 0 bytes in 0 blocks
==27871==      possibly lost: 0 bytes in 0 blocks
==27871==    still reachable: 13,967 bytes in 8 blocks
==27871==         suppressed: 0 bytes in 0 blocks
==27871== Rerun with --leak-check=full to see details of leaked memory
==27871== 
==27871== For counts of detected and suppressed errors, rerun with: -v
==27871== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 1 from 1)