[asterisk-bugs] [Asterisk 0010325]: chan_skinny randomly crashing asterisk

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=10325 
====================================================================== 
Reported By:                sbisker
Assigned To:                qwell
====================================================================== 
Project:                    Asterisk
Issue ID:                   10325
Category:                   Channels/chan_skinny
Reproducibility:            random
Severity:                   crash
Priority:                   normal
Status:                     assigned
Asterisk Version:            SVN 
SVN Branch (only for SVN checkouts, not tarball releases):  1.4  
SVN Revision (number only!): 77071 
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             07-27-2007 13:54 CDT
Last Modified:              07-27-2007 17:04 CDT
====================================================================== 
Summary:                    chan_skinny randomly crashing asterisk
Description: 
This is the fifth time in as many days that asterisk has core dumped. 
Every time the backtrace looks mangled like this one.  I'll upload just
after I post.


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

---------------------------------------------------------------------- 
 wedhorn - 07-27-07 17:04  
---------------------------------------------------------------------- 
Your issues seems to be this at about line 1550:

	if (skinnydebug)
			ast_verbose("Setting Callinfo to %s(%s) from %s(%s) on %s(%d)\n",
fromname, fromnum, toname, tonum, s->device->name, instance);

That reference to s->device->name is not valid as s=NULL. If you turn
skinnydebug off, it should stop these crashes, or you could replace
s->device->name in the above line to
(s?s->device->name:"unregistered_device").

However, there is still the underlying issue that your unregistered phone
is making a call.

More generally, rather than sending s to all the transmit_ procs, why
don't we send d as it would generally be more useful and we can allocate s
(d->s) in transmit_response.

More generally 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
07-27-07 17:04  wedhorn        Note Added: 0067998                          
======================================================================