[asterisk-users] Seg Fault after upgrade to Asterisk 1.6.0.8

[Mark Michelson]

M Hulber wrote:
> Went from 1.6.0.6 to 1.6.0.8 and resulted in segmentation fault.  
> Reverted to 1.6.0.6 and back to normal.
> 
> ------------------
> 
> Linux asterisk.hulber.com 2.6.18-128.1.1.el5 #1 SMP Mon Jan 26 13:58:24 
> EST 2009 x86_64 x86_64 x86_64 GNU/Linux
> 
> Apr  3 11:49:56 asterisk kernel: asterisk[3780]: segfault at 
> 00002ce1ac0537a8 rip 0000003e980715a8 rsp 00007fff5bf00c30 error 4
> Apr  3 11:50:00 asterisk kernel: asterisk[3828]: segfault at 
> 0000000004000000 rip 0000003e980758d9 rsp 00007fffd3138ef0 error 4
> Apr  3 11:50:04 asterisk kernel: asterisk[3879]: segfault at 
> 000000000c000000 rip 0000003e980758d9 rsp 00007fffde4cf280 error 4
> Apr  3 11:50:09 asterisk kernel: asterisk[3927]: segfault at 
> 000000001c000000 rip 0000003e980758d9 rsp 00007fff2fd65b10 error 4
> Apr  3 11:50:13 asterisk kernel: asterisk[3973]: segfault at 
> 00002ce1ac04f948 rip 0000003e980715a8 rsp 00007fff6c283fb0 error 4
> Apr  3 11:50:17 asterisk kernel: asterisk[4022]: segfault at 
> 00002ce1ac0486e8 rip 0000003e980715a8 rsp 00007fff4e1d0f00 error 4
> Apr  3 11:50:21 asterisk kernel: asterisk[4069]: segfault at 
> 00002ce1ac067e28 rip 0000003e980715a8 rsp 00007fff2f3ee120 error 4
> 
> Asterisk ended with exit status 139
> Asterisk exited on signal 11.
> Automatically restarting Asterisk.
> mpg123: no process killed
> /usr/sbin/safe_asterisk: line 117:  5322 Segmentation fault      (core 
> dumped) nice -n $PRIORITY ${ASTSBINDIR}/asterisk -f ${CLIARGS} 
> ${ASTARGS} >&/dev/${TTY} < /dev/${TTY}
> Asterisk ended with exit status 139
> Asterisk exited on signal 11.
> Automatically restarting Asterisk.
> mpg123: no process killed
> /usr/sbin/safe_asterisk: line 117:  5372 Segmentation fault      (core 
> dumped) nice -n $PRIORITY ${ASTSBINDIR}/asterisk -f ${CLIARGS} 
> ${ASTARGS} >&/dev/${TTY} < /dev/${TTY}
> Asterisk ended with exit status 139
> Asterisk exited on signal 11.
> Automatically restarting Asterisk.
> mpg123: no process killed
> /usr/sbin/safe_asterisk: line 117:  5419 Segmentation fault      (core 
> dumped) nice -n $PRIORITY ${ASTSBINDIR}/asterisk -f ${CLIARGS} 
> ${ASTARGS} >&/dev/${TTY} < /dev/${TTY}
> Asterisk ended with exit status 139
> Asterisk exited on signal 11.
> Automatically restarting Asterisk.
> mpg123: no process killed
> /usr/sbin/safe_asterisk: line 117:  5467 Segmentation fault      (core 
> dumped) nice -n $PRIORITY ${ASTSBINDIR}/asterisk -f ${CLIARGS} 
> ${ASTARGS} >&/dev/${TTY} < /dev/${TTY}
> Asterisk ended with exit status 139
> Asterisk exited on signal 11.
> Automatically restarting Asterisk.
> mpg123: no process killed
> /usr/sbin/safe_asterisk: line 117:  5514 Segmentation fault      (core 
> dumped) nice -n $PRIORITY ${ASTSBINDIR}/asterisk -f ${CLIARGS} 
> ${ASTARGS} >&/dev/${TTY} < /dev/${TTY}
> Asterisk ended with exit status 139
> Asterisk exited on signal 11.
> Automatically restarting Asterisk.
> 

Thanks for the information. Could you open a bug report at 
http://bugs.digium.com and upload a backtrace from the core dumps? Instructions 
for uploading a backtrace can be found in doc/backtrace.txt in the Asterisk source.

I suspect this is a regression introduced between 1.6.0.6 and 1.6.0.7 since 
1.6.0.8 is exactly the same as 1.6.0.7, except for the security fix for 
AST-2009-003.

Mark Michelson