[asterisk-bugs] [Asterisk 0012362]: Asterisk crashes everytime i try to dial a realtime peer. e.g.DIAL(SIP/peer/number, 60, tTwW)

[noreply at bugs.digium.com]

email_notification_title_for_status_bug_ready_for_testing 
====================================================================== 
http://bugs.digium.com/view.php?id=12362 
====================================================================== 
Reported By:                vinsik
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   12362
Category:                   Channels/chan_sip/General
Reproducibility:            always
Severity:                   crash
Priority:                   normal
Status:                     ready for testing
Asterisk Version:           1.4.19 
SVN Branch (only for SVN checkouts, not tarball releases):  1.4  
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             04-03-2008 07:36 CDT
Last Modified:              04-03-2008 08:57 CDT
====================================================================== 
Summary:                    Asterisk crashes everytime i try to dial a realtime
peer. e.g.DIAL(SIP/peer/number,60,tTwW)
Description: 
Asterisk crashes everytime i try to dial a realtime peer.

Command line output:
-- AGI Script Executing Application: (SET) Options:
(CDR(accountcode)=10000)
-- AGI Script Executing Application: (SET) Options:
(CALLERID(num)=123456)
-- AGI Script Executing Application: (DIAL) Options:
(SIP/roxser/123456|60|tTwW)
Disconnected from Asterisk server

Local realtime users work fine. Also all local CMD's work.
Cannot find an logical reason. Reverting back to 1.4.18, as it works ok.


Attached is GDB of asterisk process. 
Asterisk debug does not reveal anything relevant.
====================================================================== 

---------------------------------------------------------------------- 
 putnopvut - 04-03-08 08:57  
---------------------------------------------------------------------- 
The problem appeared to stem from a memcmp that involved a NULL sockaddr_in
pointer. I have uploaded a potential patch for this. The logic seems right
by me, but I'd appreciate it if you'd give it a quick test to be sure that
it works as I expect it to.

As snuffy noted, for future backtraces, if you could upload unoptimized
backtraces  it is generally more helpful. Although, instead of "dont
compile' I believe he meant to say to select the DONT_OPTIMIZE flag in the
"compile options" section of menuselect.

Thanks for reporting this! 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
04-03-08 08:57  putnopvut      Note Added: 0084984                          
04-03-08 08:57  putnopvut      Status                   new => ready for testing
======================================================================