[asterisk-users] segfault - asterisk crash and restart

[Atis Lezdins]

Rilawich Ango wrote:
> Hi all,
> 
>   Recently, I have upgraded the asterisk as following.
> asterisk-1.4.13
> asterisk-addon-1.4.4
> libpri-1.4.1
> zaptel-1.4.5.1
> Usage of the server: inbound and outbound call, queue, mixmonitor, meetme, moh
>   After upgrade, the server get segfault randomly and asterisk crash
> and restart itself.  I got 2 core dumps of the segfault.  Based on the
> core dump, we can't figure out the root cause to the problem as the
> content of the core dump is not the same.  We have no idea what the
> problem is.  Anyone can give me some advices.
> 
> --core dump 1--
> (gdb) bt full
> #0  0x00000037e806e1f3 in _int_free () from /lib64/libc.so.6
> No symbol table info available.
> #1  0x00000037e8071fac in free () from /lib64/libc.so.6
> No symbol table info available.
> #2  0x000000000046b7b7 in ast_frame_free (fr=0x1b9da4b0, cache=0)
>     at frame.c:369
> No locals.
> #3  0x00002aaab1173573 in mixmonitor_thread (obj=0x1bb08220)
>    from /usr/lib/asterisk/modules/app_mixmonitor.so

This is clearly mixmonitor-related. I suggest you to look for similar
mixmonitor bugs in digium's mantis - if there's none, create and attach
this backtrace.

[snip]

> --core dump 2--
> 
> Core was generated by `/usr/sbin/asterisk -f -vvvg -c'.
> Program terminated with signal 11, Segmentation fault.
> #0  0x000000000044da80 in ast_var_name (var=0x10f1d58a0) at chanvars.c:69
> 69		if (name[0] == '_') {
> (gdb) bt full
> #0  0x000000000044da80 in ast_var_name (var=0x10f1d58a0) at chanvars.c:69
> 	name = 0x10f1d58b0 <Address 0x10f1d58b0 out of bounds>
> #1  0x000000000049948f in pbx_builtin_setvar_helper (chan=0xf460320,
> name=0x2aaabf53cbf7 "DIALSTATUS",
>     value=0x417a0690 "BUSY") at pbx.c:5825
> 	newvariable = (struct ast_var_t *) 0x10f1d58a0
> 	headp = (struct varshead *) 0xf460880
> 	nametail = 0x2aaabf53cbf7 "DIALSTATUS"
> 	__PRETTY_FUNCTION__ = "pbx_builtin_setvar_helper"

Great, this confirms that i'm not the only one having this problem. Can
you please add this to http://bugs.digium.com/view.php?id=10923

As from my knowledge - this will happen often on 1.4.13.. The safe
version i'm using is 1.4.10, but 1.4.12.1 already have this problem..

Regards,
Atis