[asterisk-bugs] [Asterisk 0013526]: Last 1.4 svn crash. Backtrace attached

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=13526 
====================================================================== 
Reported By:                slavon
Assigned To:                murf
====================================================================== 
Project:                    Asterisk
Issue ID:                   13526
Category:                   CDR/General
Reproducibility:            always
Severity:                   crash
Priority:                   normal
Status:                     feedback
Asterisk Version:           SVN 
SVN Branch (only for SVN checkouts, not tarball releases):  1.4  
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             2008-09-20 07:04 CDT
Last Modified:              2008-10-13 18:32 CDT
====================================================================== 
Summary:                    Last 1.4 svn crash. Backtrace attached
Description: 
Hello all.

Last 1.4 svn crash. Backtrace and valgrind attached

Thanks
======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
related to          0013490 crash in ast_cdr_start, backtraces atta...
====================================================================== 

---------------------------------------------------------------------- 
 (0093569) murf (administrator) - 2008-10-13 18:32
 http://bugs.digium.com/view.php?id=13526#c93569 
---------------------------------------------------------------------- 
slavon--

This bug has been in feedback mode for a while. I shall probably give it
another
day, and close it with status "suspended", and you'll be able to re-open
it when you have more info.

I have tried to reproduce the valgrind results you reported, but with
blind xfers, it did not have any problems. The gdb stack trace reports a
crash in the sip channel driver, the valgrind report memory errors in
specialized_reset, but I need to know exactly what kind of xfer gave these
results! 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2008-10-13 18:32 murf           Note Added: 0093569                          
======================================================================