[asterisk-bugs] [Asterisk 0012075]: Segmentation Fault when Calling app Voicemail after Blind Transfer

noreply at bugs.digium.com noreply at bugs.digium.com
Thu May 29 09:47:43 CDT 2008


A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=12075 
====================================================================== 
Reported By:                darrylc
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   12075
Category:                   Applications/app_voicemail
Reproducibility:            always
Severity:                   crash
Priority:                   normal
Status:                     feedback
Asterisk Version:           1.4.18 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             02-26-2008 09:55 CST
Last Modified:              05-29-2008 09:47 CDT
====================================================================== 
Summary:                    Segmentation Fault when Calling app Voicemail after
Blind Transfer
Description: 
So I have a macro called macro-staff which is used to handle extension to
extension dialing.  The macro works perfectly for everything except BLIND
call transfers.  In features.conf the blind transfer key is set to '##' so
if you press '##' during a call Asterisk will prompt you for the extension
you wish to blind transfer the call to.

Here is the situation.  The transfer actually works, so when you press
'#http://bugs.digium.com/view.php?id=100#' as an example the call is properly
transfered to extension 100. 
The problem is if extensions 100 does not answer, macro-staff tries to send
the call into Voicemail(100) and as soon as that happens Asterisk does a
Segmentation fault.

Interestingly enough if you do a transfer from the phone, using the
Transfer button on the acutal phone, and extension 100 does not answer, and
VoiceMail(100) is called from inside macro-staff, there is NO segmentation
fault.  It only does a segmentation fault when it reaches voicemail from a
blind transfer using the '##'.

macro-staff runs no matter what, so if you press '##' to do a blind
transfer, macro-staff is called (nested) just the same as it would be if
you transfer the call using the transfer button on the phone.  So either
way there is a nested call to macro-staff, but only one when using the
'##', (blind transfer) does a segmentation fault happen.


====================================================================== 

---------------------------------------------------------------------- 
 darrylc - 05-29-08 09:47  
---------------------------------------------------------------------- 
My apologies for not doing this last week as was my intent.  I got caught
up with other projects so sorry about that.

Ok so looks like this bug is confirmed now.  I compiled back Asterisk to
the way it was before with 'DONT_OPTIMIZE' disabled and the problem is
happening again (Segmentation Faults on Blind Transfers).

Every time I do a blind transfer Asterisk seg faults.  So looks like
Corydon76 may have been onto something when he suggested it may be some
sort of gcc bug.

So this message is just to confirm that if I compile with 'DONT_OPTIMIZE'
'enabled' the segmentation fault does not happen, but if I compile with
'DONT_OPTIMIZE' 'disabled' then the segmentation fault happens everytime I
do a blind transfer.

Hope this helps and please do let me know if you need any clarification.

Cheers! 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
05-29-08 09:47  darrylc        Note Added: 0087495                          
======================================================================




More information about the asterisk-bugs mailing list