==5390== Memcheck, a memory error detector
==5390== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al.
==5390== Using Valgrind-3.10.0 and LibVEX; rerun with -h for copyright info
==5390== Command: binutils-gdb/binutils/objdump -afphxgGtTrRwW --special-syms 102-3196-0.004
==5390== Parent PID: 7579
==5390== 
==5390== Invalid write of size 1
==5390==    at 0x52D54A3: __GI_mempcpy (memcpy.S:167)
==5390==    by 0x52C436D: _IO_file_xsgetn (fileops.c:1399)
==5390==    by 0x52BA227: fread (iofread.c:42)
==5390==    by 0x85FB87: cache_bread_1 (cache.c:316)
==5390==    by 0x85FB87: cache_bread (cache.c:350)
==5390==    by 0x4FA371: bfd_bread (bfdio.c:196)
==5390==    by 0x618405: vms_get_remaining_object_record (vms-alpha.c:833)
==5390==    by 0x6224DB: alpha_vms_object_p (vms-alpha.c:2550)
==5390==    by 0x4FE6A6: bfd_check_format_matches (format.c:305)
==5390==    by 0x40D6B1: display_object_bfd (objdump.c:3328)
==5390==    by 0x40D6B1: display_any_bfd (objdump.c:3404)
==5390==    by 0x40F7B2: display_file (objdump.c:3425)
==5390==    by 0x40A079: main (objdump.c:3707)
==5390==  Address 0x55fddac is 0 bytes after a block of size 12 alloc'd
==5390==    at 0x4C27C20: malloc (vg_replace_malloc.c:296)
==5390==    by 0x4FEF3D: bfd_malloc (libbfd.c:181)
==5390==    by 0x622429: alpha_vms_object_p (vms-alpha.c:2467)
==5390==    by 0x4FE6A6: bfd_check_format_matches (format.c:305)
==5390==    by 0x40D6B1: display_object_bfd (objdump.c:3328)
==5390==    by 0x40D6B1: display_any_bfd (objdump.c:3404)
==5390==    by 0x40F7B2: display_file (objdump.c:3425)
==5390==    by 0x40A079: main (objdump.c:3707)
==5390== 
==5390== Invalid write of size 8
==5390==    at 0x52D555B: __GI_mempcpy (memcpy.S:272)
==5390==    by 0x52C436D: _IO_file_xsgetn (fileops.c:1399)
==5390==    by 0x52BA227: fread (iofread.c:42)
==5390==    by 0x85FB87: cache_bread_1 (cache.c:316)
==5390==    by 0x85FB87: cache_bread (cache.c:350)
==5390==    by 0x4FA371: bfd_bread (bfdio.c:196)
==5390==    by 0x618405: vms_get_remaining_object_record (vms-alpha.c:833)
==5390==    by 0x6224DB: alpha_vms_object_p (vms-alpha.c:2550)
==5390==    by 0x4FE6A6: bfd_check_format_matches (format.c:305)
==5390==    by 0x40D6B1: display_object_bfd (objdump.c:3328)
==5390==    by 0x40D6B1: display_any_bfd (objdump.c:3404)
==5390==    by 0x40F7B2: display_file (objdump.c:3425)
==5390==    by 0x40A079: main (objdump.c:3707)
==5390==  Address 0x55fddb0 is 4 bytes after a block of size 12 alloc'd
==5390==    at 0x4C27C20: malloc (vg_replace_malloc.c:296)
==5390==    by 0x4FEF3D: bfd_malloc (libbfd.c:181)
==5390==    by 0x622429: alpha_vms_object_p (vms-alpha.c:2467)
==5390==    by 0x4FE6A6: bfd_check_format_matches (format.c:305)
==5390==    by 0x40D6B1: display_object_bfd (objdump.c:3328)
==5390==    by 0x40D6B1: display_any_bfd (objdump.c:3404)
==5390==    by 0x40F7B2: display_file (objdump.c:3425)
==5390==    by 0x40A079: main (objdump.c:3707)
==5390== 

valgrind: m_mallocfree.c:304 (get_bszB_as_is): Assertion 'bszB_lo == bszB_hi' failed.
valgrind: Heap block lo/hi size mismatch: lo = 80, hi = 18067175071813632.
This is probably caused by your program erroneously writing past the
end of a heap block and corrupting heap metadata.  If you fix any
invalid writes reported by Memcheck, this assertion failure will
probably go away.  Please try that before reporting this as a bug.


host stacktrace:
==5390==    at 0x380A488F: show_sched_status_wrk (m_libcassert.c:319)
==5390==    by 0x380A4984: report_and_quit (m_libcassert.c:390)
==5390==    by 0x380A4B06: vgPlain_assert_fail (m_libcassert.c:455)
==5390==    by 0x380B165D: get_bszB_as_is (m_mallocfree.c:302)
==5390==    by 0x380B165D: get_bszB (m_mallocfree.c:312)
==5390==    by 0x380B165D: get_pszB (m_mallocfree.c:386)
==5390==    by 0x380B165D: vgPlain_describe_arena_addr (m_mallocfree.c:1532)
==5390==    by 0x3809DC53: vgPlain_describe_addr (m_addrinfo.c:188)
==5390==    by 0x3809C6C3: vgMemCheck_update_Error_extra (mc_errors.c:1147)
==5390==    by 0x380A057A: vgPlain_maybe_record_error (m_errormgr.c:818)
==5390==    by 0x3809BEBB: vgMemCheck_record_memparam_error (mc_errors.c:813)
==5390==    by 0x38076373: check_mem_is_addressable (mc_main.c:3940)
==5390==    by 0x380F8020: vgPlain_client_syscall (syswrap-main.c:1586)
==5390==    by 0x380F48FA: handle_syscall (scheduler.c:1103)
==5390==    by 0x380F5FD6: vgPlain_scheduler (scheduler.c:1416)
==5390==    by 0x38105860: thread_wrapper (syswrap-linux.c:103)
==5390==    by 0x38105860: run_a_thread_NORETURN (syswrap-linux.c:156)

sched status:
  running_tid=1

Thread 1: status = VgTs_Runnable
==5390==    at 0x5328F20: __read_nocancel (syscall-template.S:81)
==5390==    by 0x52C42A8: _IO_file_xsgetn (fileops.c:1441)
==5390==    by 0x52BA227: fread (iofread.c:42)
==5390==    by 0x85FB87: cache_bread_1 (cache.c:316)
==5390==    by 0x85FB87: cache_bread (cache.c:350)
==5390==    by 0x4FA371: bfd_bread (bfdio.c:196)
==5390==    by 0x618405: vms_get_remaining_object_record (vms-alpha.c:833)
==5390==    by 0x6224DB: alpha_vms_object_p (vms-alpha.c:2550)
==5390==    by 0x4FE6A6: bfd_check_format_matches (format.c:305)
==5390==    by 0x40D6B1: display_object_bfd (objdump.c:3328)
==5390==    by 0x40D6B1: display_any_bfd (objdump.c:3404)
==5390==    by 0x40F7B2: display_file (objdump.c:3425)
==5390==    by 0x40A079: main (objdump.c:3707)


Note: see also the FAQ in the source distribution.
It contains workarounds to several common problems.
In particular, if Valgrind aborted or crashed after
identifying problems in your program, there's a good chance
that fixing those problems will prevent Valgrind aborting or
crashing, especially if it happened in m_mallocfree.c.

If that doesn't help, please report this bug to: www.valgrind.org

In the bug report, send all the above text, the valgrind
version, and what OS and version you are using.  Thanks.