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