[asterisk-bugs] [Asterisk 0015249]: crash - address out of bounds

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=15249 
====================================================================== 
Reported By:                pj
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   15249
Category:                   Channels/chan_sip/General
Reproducibility:            random
Severity:                   crash
Priority:                   normal
Status:                     new
Asterisk Version:           SVN 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases):  trunk 
SVN Revision (number only!): 198498 
Request Review:              
====================================================================== 
Date Submitted:             2009-06-02 04:37 CDT
Last Modified:              2009-06-02 06:24 CDT
====================================================================== 
Summary:                    crash - address out of bounds
Description: 
asterisk crashed during call ringing state, it was sip2sip call, so it's
probably bug in chan_sip, but I'm also using chan_skinny, so please look at
bugreport https://issues.asterisk.org/view.php?id=13777 if it can't be related.
====================================================================== 

---------------------------------------------------------------------- 
 (0105881) davidw (reporter) - 2009-06-02 06:24
 https://issues.asterisk.org/view.php?id=15249#c105881 
---------------------------------------------------------------------- 
Thread 21 is in the kernel.  Kernel detected errors are normally reported
as return codes, not as signals.

Thread 1 appears to be in a run state and is executing from
handle_stimulus_message in chan_skinny.c.  A much more plausible situation
for a crash.

"Address out of bounds" is not a normal Unix signal.  It is more likely to
be gdb reporting that it cannot fully interpret what it has been given.

When you start gdb, it should tell you the signal that caused the crash. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-06-02 06:24 davidw         Note Added: 0105881                          
======================================================================