==4855== Memcheck, a memory error detector
==4855== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al.
==4855== Using Valgrind-3.10.0 and LibVEX; rerun with -h for copyright info
==4855== Command: binutils-gdb/binutils/objdump -afphxgGtTrRwW --special-syms 8396-1185-0.004
==4855== Parent PID: 2103
==4855== 
==4855== Invalid read of size 8
==4855==    at 0x40C4E0: dump_reloc_set (objdump.c:3003)
==4855==    by 0x40DBB2: dump_relocs_in_section (objdump.c:3132)
==4855==    by 0x50188B: bfd_map_over_sections (section.c:1354)
==4855==    by 0x40D2AD: dump_relocs (objdump.c:3141)
==4855==    by 0x40D2AD: dump_bfd (objdump.c:3267)
==4855==    by 0x40D6EF: display_object_bfd (objdump.c:3330)
==4855==    by 0x40D6EF: display_any_bfd (objdump.c:3404)
==4855==    by 0x40F7B2: display_file (objdump.c:3425)
==4855==    by 0x40A079: main (objdump.c:3707)
==4855==  Address 0x17ae578 is not stack'd, malloc'd or (recently) free'd
==4855== 
==4855== 
==4855== Process terminating with default action of signal 11 (SIGSEGV)
==4855==  Access not within mapped region at address 0x17AE578
==4855==    at 0x40C4E0: dump_reloc_set (objdump.c:3003)
==4855==    by 0x40DBB2: dump_relocs_in_section (objdump.c:3132)
==4855==    by 0x50188B: bfd_map_over_sections (section.c:1354)
==4855==    by 0x40D2AD: dump_relocs (objdump.c:3141)
==4855==    by 0x40D2AD: dump_bfd (objdump.c:3267)
==4855==    by 0x40D6EF: display_object_bfd (objdump.c:3330)
==4855==    by 0x40D6EF: display_any_bfd (objdump.c:3404)
==4855==    by 0x40F7B2: display_file (objdump.c:3425)
==4855==    by 0x40A079: main (objdump.c:3707)
==4855==  If you believe this happened as a result of a stack
==4855==  overflow in your program's main thread (unlikely but
==4855==  possible), you can try to increase the size of the
==4855==  main thread stack using the --main-stacksize= flag.
==4855==  The main thread stack size used in this run was 8388608.
==4855== 
==4855== HEAP SUMMARY:
==4855==     in use at exit: 45,568 bytes in 12 blocks
==4855==   total heap usage: 27 allocs, 15 frees, 96,536 bytes allocated
==4855== 
==4855== LEAK SUMMARY:
==4855==    definitely lost: 0 bytes in 0 blocks
==4855==    indirectly lost: 0 bytes in 0 blocks
==4855==      possibly lost: 0 bytes in 0 blocks
==4855==    still reachable: 45,568 bytes in 12 blocks
==4855==         suppressed: 0 bytes in 0 blocks
==4855== Rerun with --leak-check=full to see details of leaked memory
==4855== 
==4855== For counts of detected and suppressed errors, rerun with: -v
==4855== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 1 from 1)