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