[Home]

Summary:ASTERISK-12884: SegFault when after saying "Thank you" when user presses # or just hangs up
Reporter:jmb287 (jmb287)Labels:
Date Opened:2008-10-13 14:00:41Date Closed:2011-06-07 14:00:55
Priority:BlockerRegression?No
Status:Closed/CompleteComponents:Applications/app_voicemail
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:
Description:User calls into system, leaves voicemail, presses # to exit, system says Thank You and then segfaults.


****** STEPS TO REPRODUCE ******

See above Description

****** ADDITIONAL INFORMATION ******

 == Everyone is busy/congested at this time (1:0/0/1)
   -- Executing [s@macro-vPBX-dial-with-vm:3] VoiceMail("DAHDI/23-1", "100@vPBX-140") in new stack
   -- <DAHDI/23-1> Playing 'vm-intro.gsm' (language 'en')
   -- DAHDI/1-1 answered SIP/15059386309-ac075e80
   -- <DAHDI/23-1> Playing 'beep.gsm' (language 'en')
   -- Recording the message
   -- x=0, open writing:  /var/spool/asterisk/voicemail/vPBX-140/100/tmp/aS7q0V format: wav49, 0x2aaaac07b0d0
   -- x=1, open writing:  /var/spool/asterisk/voicemail/vPBX-140/100/tmp/aS7q0V format: gsm, 0x2aaaac080bc0
   -- x=2, open writing:  /var/spool/asterisk/voicemail/vPBX-140/100/tmp/aS7q0V format: wav, 0x2aaaac081e70
   -- User ended message by pressing #
   -- <DAHDI/23-1> Playing 'auth-thankyou.gsm' (language 'en')
voip01*CLI>
Disconnected from Asterisk server
/usr/sbin/safe_asterisk: line 138: 13250 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.
[root@voip01 asterisk]# Automatically restarting Asterisk.
mpg123: no process killed
Comments:By: jmb287 (jmb287) 2008-10-13 14:49:55

Update,  this problem does not appear in
Asterisk SVN-branch-1.6.1-r148562 built by root @ voip01 on a x86_64 running Linux on 2008-10-13 19:54:17 UTC
By: Mark Michelson (mmichelson) 2008-10-13 15:04:19

Two things:

1. Could you check to see if the 1.6.0 branch of SVN still has this issue?

2. If it does, could you please upload a backtrace from an unoptimized build? Instructions for how to get a backtrace are located in doc/backtrace.txt of the Asterisk source.

Thanks!
By: Jason Parker (jparker) 2008-10-23 17:23:39

Any update here?  If we don't get a response, we aren't going to have any choice but to close this.
By: Jose Roberto Gutierrez (jrgutier) 2008-11-10 02:55:03.000-0600

I also have this problem with 1.6.0.1. RHEL5.2 x86_64. Except it segfaulted after the beep sound.

When I was trying to give you guys a backtrace and turned off optimizations, it started working. Did you want me to still give you one with optimizations?


By: Tilghman Lesher (tilghman) 2008-11-10 11:49:52.000-0600

In that case, please read doc/valgrind.txt and follow the instructions there.  Please note that even if Asterisk does not crash, it is likely that valgrind will log the information necessary to track down this issue, as long as you exactly reproduce the behavior necessary to cause this crash.
By: Tilghman Lesher (tilghman) 2008-12-18 14:11:48.000-0600

No response from reporter.