==26775== Massif, a heap profiler
==26775== Copyright (C) 2003-2013, and GNU GPL'd, by Nicholas Nethercote
==26775== Using Valgrind-3.9.0 and LibVEX; rerun with -h for copyright info
==26775== Command: asterisk -c
==26775== Parent PID: 2958
==26775== 

valgrind: m_mallocfree.c:303 (get_bszB_as_is): Assertion 'bszB_lo == bszB_hi' failed.
valgrind: Heap block lo/hi size mismatch: lo = 1, hi = 0.
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.

==26775==    at 0x3802468C: ??? (in /usr/lib64/valgrind/massif-amd64-linux)
==26775==    by 0x380247E6: ??? (in /usr/lib64/valgrind/massif-amd64-linux)
==26775==    by 0x38031506: ??? (in /usr/lib64/valgrind/massif-amd64-linux)
==26775==    by 0x3806F4BD: ??? (in /usr/lib64/valgrind/massif-amd64-linux)
==26775==    by 0x3802912F: ??? (in /usr/lib64/valgrind/massif-amd64-linux)
==26775==    by 0x380294CA: ??? (in /usr/lib64/valgrind/massif-amd64-linux)
==26775==    by 0x3807DFE4: ??? (in /usr/lib64/valgrind/massif-amd64-linux)

sched status:
  running_tid=1

Thread 1: status = VgTs_Runnable
==26775==    at 0x4C27037: free (in /usr/lib64/valgrind/vgpreload_massif-amd64-linux.so)
==26775==    by 0x518FAFB: __libc_freeres (in /usr/lib64/libc-2.18.so)
==26775==    by 0x4A226B4: _vgnU_freeres (in /usr/lib64/valgrind/vgpreload_core-amd64-linux.so)
==26775==    by 0x50670AA: __run_exit_handlers (in /usr/lib64/libc-2.18.so)
==26775==    by 0x5067134: exit (in /usr/lib64/libc-2.18.so)
==26775==    by 0x445E1F: really_quit (asterisk.c:1925)
==26775==    by 0x4455E3: quit_handler (asterisk.c:1736)
==26775==    by 0x446769: handle_stop_gracefully (asterisk.c:2237)
==26775==    by 0x4A39A8: ast_cli_command_full (cli.c:2691)
==26775==    by 0x44629C: consolehandler (asterisk.c:2094)
==26775==    by 0x44D03C: main (asterisk.c:4412)


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.