==28500== Memcheck, a memory error detector
==28500== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al.
==28500== Using Valgrind-3.10.0 and LibVEX; rerun with -h for copyright info
==28500== Command: binutils-gdb/binutils/objdump -afphxgGWtTrRw --special-syms 078-18333-0.001:0.1
==28500== Parent PID: 28498
==28500== 
==28500== Invalid read of size 8
==28500==    at 0x4322D8: parse_coff_type (rdcoff.c:211)
==28500==    by 0x432EAC: parse_coff (rdcoff.c:863)
==28500==    by 0x41DC9F: read_debugging_info (rddbg.c:79)
==28500==    by 0x4079B2: dump_bfd (objdump.c:3271)
==28500==    by 0x407F1F: display_object_bfd (objdump.c:3322)
==28500==    by 0x407F1F: display_any_bfd (objdump.c:3396)
==28500==    by 0x409FD2: display_file (objdump.c:3417)
==28500==    by 0x4048F9: main (objdump.c:3699)
==28500==  Address 0xfffffffc056184b8 is not stack'd, malloc'd or (recently) free'd
==28500== 
==28500== 
==28500== Process terminating with default action of signal 11 (SIGSEGV)
==28500==  Access not within mapped region at address 0xFFFFFFFC056184B8
==28500==    at 0x4322D8: parse_coff_type (rdcoff.c:211)
==28500==    by 0x432EAC: parse_coff (rdcoff.c:863)
==28500==    by 0x41DC9F: read_debugging_info (rddbg.c:79)
==28500==    by 0x4079B2: dump_bfd (objdump.c:3271)
==28500==    by 0x407F1F: display_object_bfd (objdump.c:3322)
==28500==    by 0x407F1F: display_any_bfd (objdump.c:3396)
==28500==    by 0x409FD2: display_file (objdump.c:3417)
==28500==    by 0x4048F9: main (objdump.c:3699)
==28500==  If you believe this happened as a result of a stack
==28500==  overflow in your program's main thread (unlikely but
==28500==  possible), you can try to increase the size of the
==28500==  main thread stack using the --main-stacksize= flag.
==28500==  The main thread stack size used in this run was 8388608.
==28500== 
==28500== HEAP SUMMARY:
==28500==     in use at exit: 77,626 bytes in 23 blocks
==28500==   total heap usage: 44 allocs, 21 frees, 125,223 bytes allocated
==28500== 
==28500== LEAK SUMMARY:
==28500==    definitely lost: 0 bytes in 0 blocks
==28500==    indirectly lost: 0 bytes in 0 blocks
==28500==      possibly lost: 0 bytes in 0 blocks
==28500==    still reachable: 77,626 bytes in 23 blocks
==28500==         suppressed: 0 bytes in 0 blocks
==28500== Rerun with --leak-check=full to see details of leaked memory
==28500== 
==28500== For counts of detected and suppressed errors, rerun with: -v
==28500== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 1 from 1)