==8976== Memcheck, a memory error detector
==8976== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al.
==8976== Using Valgrind-3.10.0 and LibVEX; rerun with -h for copyright info
==8976== Command: binutils-gdb/binutils/objdump -afphxgGtTrRwW --special-syms samples/54f733e0
==8976== Parent PID: 8975
==8976== 
==8976== Invalid read of size 8
==8976==    at 0x83CE3B: process_otr (versados.c:424)
==8976==    by 0x83D82F: versados_pass_2 (versados.c:666)
==8976==    by 0x83D9D4: versados_canonicalize_symtab (versados.c:726)
==8976==    by 0x40D3F3: slurp_symtab (objdump.c:573)
==8976==    by 0x40D3F3: dump_bfd (objdump.c:3276)
==8976==    by 0x40DF27: display_object_bfd (objdump.c:3364)
==8976==    by 0x40DF27: display_any_bfd (objdump.c:3446)
==8976==    by 0x40FEA2: display_file (objdump.c:3467)
==8976==    by 0x40A849: main (objdump.c:3749)
==8976==  Address 0x78 is not stack'd, malloc'd or (recently) free'd
==8976== 
==8976== 
==8976== Process terminating with default action of signal 11 (SIGSEGV)
==8976==  Access not within mapped region at address 0x78
==8976==    at 0x83CE3B: process_otr (versados.c:424)
==8976==    by 0x83D82F: versados_pass_2 (versados.c:666)
==8976==    by 0x83D9D4: versados_canonicalize_symtab (versados.c:726)
==8976==    by 0x40D3F3: slurp_symtab (objdump.c:573)
==8976==    by 0x40D3F3: dump_bfd (objdump.c:3276)
==8976==    by 0x40DF27: display_object_bfd (objdump.c:3364)
==8976==    by 0x40DF27: display_any_bfd (objdump.c:3446)
==8976==    by 0x40FEA2: display_file (objdump.c:3467)
==8976==    by 0x40A849: main (objdump.c:3749)
==8976==  If you believe this happened as a result of a stack
==8976==  overflow in your program's main thread (unlikely but
==8976==  possible), you can try to increase the size of the
==8976==  main thread stack using the --main-stacksize= flag.
==8976==  The main thread stack size used in this run was 8388608.
==8976== 
==8976== HEAP SUMMARY:
==8976==     in use at exit: 9,168 bytes in 17 blocks
==8976==   total heap usage: 28 allocs, 11 frees, 58,502 bytes allocated
==8976== 
==8976== LEAK SUMMARY:
==8976==    definitely lost: 2 bytes in 1 blocks
==8976==    indirectly lost: 0 bytes in 0 blocks
==8976==      possibly lost: 0 bytes in 0 blocks
==8976==    still reachable: 9,166 bytes in 16 blocks
==8976==         suppressed: 0 bytes in 0 blocks
==8976== Rerun with --leak-check=full to see details of leaked memory
==8976== 
==8976== For counts of detected and suppressed errors, rerun with: -v
==8976== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)