==23964== Memcheck, a memory error detector ==23964== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al. ==23964== Using Valgrind-3.9.0 and LibVEX; rerun with -h for copyright info ==23964== Command: asterisk -vvvvcg ==23964== ==23964== Thread 18: ==23964== Invalid write of size 1 ==23964== at 0x547A65B: vsnprintf (in /lib64/libc-2.11.1.so) ==23964== by 0x55CB2C: __ast_debug_str_helper (strings.c:76) ==23964== by 0x56EFA7: ast_str_append_va (strings.h:805) ==23964== by 0x56F284: ast_str_append (strings.h:887) ==23964== by 0x513AF7: ast_str_substitute_variables_full (pbx.c:4364) ==23964== by 0x513E90: ast_str_substitute_variables (pbx.c:4428) ==23964== by 0x10D5F53F: ??? (func_strings.c:810) ==23964== by 0x512EEC: ast_func_read (pbx.c:4162) ==23964== by 0x5142A6: pbx_substitute_variables_helper_full (pbx.c:4540) ==23964== by 0x514846: pbx_substitute_variables_helper (pbx.c:4636) ==23964== by 0x514C5F: pbx_extension_helper (pbx.c:4718) ==23964== by 0x516C0B: ast_spawn_extension (pbx.c:5380) ==23964== Address 0xfffffffff557c705 is not stack'd, malloc'd or (recently) free'd ==23964== ==23964== ==23964== Process terminating with default action of signal 11 (SIGSEGV): dumping core ==23964== Access not within mapped region at address 0xFFFFFFFFF557C705 ==23964== at 0x547A65B: vsnprintf (in /lib64/libc-2.11.1.so) ==23964== by 0x55CB2C: __ast_debug_str_helper (strings.c:76) ==23964== by 0x56EFA7: ast_str_append_va (strings.h:805) ==23964== by 0x56F284: ast_str_append (strings.h:887) ==23964== by 0x513AF7: ast_str_substitute_variables_full (pbx.c:4364) ==23964== by 0x513E90: ast_str_substitute_variables (pbx.c:4428) ==23964== by 0x10D5F53F: ??? (func_strings.c:810) ==23964== by 0x512EEC: ast_func_read (pbx.c:4162) ==23964== by 0x5142A6: pbx_substitute_variables_helper_full (pbx.c:4540) ==23964== by 0x514846: pbx_substitute_variables_helper (pbx.c:4636) ==23964== by 0x514C5F: pbx_extension_helper (pbx.c:4718) ==23964== by 0x516C0B: ast_spawn_extension (pbx.c:5380) ==23964== If you believe this happened as a result of a stack ==23964== overflow in your program's main thread (unlikely but ==23964== possible), you can try to increase the size of the ==23964== main thread stack using the --main-stacksize= flag. ==23964== The main thread stack size used in this run was 8388608. ==23964== ==23964== HEAP SUMMARY: ==23964== in use at exit: 9,511,573 bytes in 59,594 blocks ==23964== total heap usage: 395,386 allocs, 335,792 frees, 25,568,781 bytes allocated ==23964== ==23964== LEAK SUMMARY: ==23964== definitely lost: 461 bytes in 2 blocks ==23964== indirectly lost: 0 bytes in 0 blocks ==23964== possibly lost: 4,896 bytes in 18 blocks ==23964== still reachable: 9,506,216 bytes in 59,574 blocks ==23964== suppressed: 0 bytes in 0 blocks ==23964== Rerun with --leak-check=full to see details of leaked memory ==23964== ==23964== For counts of detected and suppressed errors, rerun with: -v ==23964== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 269 from 5) ==23964== could not unlink /tmp/vgdb-pipe-from-vgdb-to-23964-by-root-on-demo.demo.local ==23964== could not unlink /tmp/vgdb-pipe-to-vgdb-from-23964-by-root-on-demo.demo.local ==23964== could not unlink /tmp/vgdb-pipe-shared-mem-vgdb-23964-by-root-on-demo.demo.local