==14314== Memcheck, a memory error detector
==14314== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al.
==14314== Using Valgrind-3.10.0 and LibVEX; rerun with -h for copyright info
==14314== Command: binutils-gdb/binutils/objdump -afphxgGtTrRwW --special-syms 3450-2098-0.004
==14314== Parent PID: 6261
==14314== 
==14314== Invalid write of size 8
==14314==    at 0x41D2D4: display_debug_frames (dwarf.c:5644)
==14314==    by 0x40FA8C: dump_dwarf_section (objdump.c:2368)
==14314==    by 0x50188B: bfd_map_over_sections (section.c:1354)
==14314==    by 0x40B593: dump_dwarf (objdump.c:2426)
==14314==    by 0x40CE64: dump_bfd (objdump.c:3263)
==14314==    by 0x40D6EF: display_object_bfd (objdump.c:3330)
==14314==    by 0x40D6EF: display_any_bfd (objdump.c:3404)
==14314==    by 0x40F7B2: display_file (objdump.c:3425)
==14314==    by 0x40A079: main (objdump.c:3707)
==14314==  Address 0x8 is not stack'd, malloc'd or (recently) free'd
==14314== 
==14314== 
==14314== Process terminating with default action of signal 11 (SIGSEGV)
==14314==  Access not within mapped region at address 0x8
==14314==    at 0x41D2D4: display_debug_frames (dwarf.c:5644)
==14314==    by 0x40FA8C: dump_dwarf_section (objdump.c:2368)
==14314==    by 0x50188B: bfd_map_over_sections (section.c:1354)
==14314==    by 0x40B593: dump_dwarf (objdump.c:2426)
==14314==    by 0x40CE64: dump_bfd (objdump.c:3263)
==14314==    by 0x40D6EF: display_object_bfd (objdump.c:3330)
==14314==    by 0x40D6EF: display_any_bfd (objdump.c:3404)
==14314==    by 0x40F7B2: display_file (objdump.c:3425)
==14314==    by 0x40A079: main (objdump.c:3707)
==14314==  If you believe this happened as a result of a stack
==14314==  overflow in your program's main thread (unlikely but
==14314==  possible), you can try to increase the size of the
==14314==  main thread stack using the --main-stacksize= flag.
==14314==  The main thread stack size used in this run was 8388608.
==14314== 
==14314== HEAP SUMMARY:
==14314==     in use at exit: 21,275 bytes in 25 blocks
==14314==   total heap usage: 58 allocs, 33 frees, 444,444 bytes allocated
==14314== 
==14314== LEAK SUMMARY:
==14314==    definitely lost: 88 bytes in 1 blocks
==14314==    indirectly lost: 6 bytes in 2 blocks
==14314==      possibly lost: 0 bytes in 0 blocks
==14314==    still reachable: 21,181 bytes in 22 blocks
==14314==         suppressed: 0 bytes in 0 blocks
==14314== Rerun with --leak-check=full to see details of leaked memory
==14314== 
==14314== For counts of detected and suppressed errors, rerun with: -v
==14314== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 1 from 1)