[asterisk-bugs] [Asterisk 0019037]: Crash when posting a CDR record

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=19037 
====================================================================== 
Reported By:                kkm
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   19037
Category:                   Resources/res_odbc
Reproducibility:            unable to reproduce
Severity:                   crash
Priority:                   normal
Status:                     new
Asterisk Version:           1.8.2.3 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2011-03-29 16:00 CDT
Last Modified:              2011-03-31 02:35 CDT
====================================================================== 
Summary:                    Crash when posting a CDR record
Description: 
Both CEL and CDR are enabled for a transition. Using ODBC driver for
Microsoft SQL. 

This is a random crash that happened only once.
====================================================================== 

---------------------------------------------------------------------- 
 (0133193) tilghman (manager) - 2011-03-31 02:35
 https://issues.asterisk.org/view.php?id=19037#c133193 
---------------------------------------------------------------------- 
The crash is actually within the pthreads library, and the crash suggests a
memory corruption problem.  You're right that this isn't necessarily an
Asterisk problem, though, especially as the mutex in question isn't in our
code; however, it's still possible that the application code is where the
memory corruption occurred.  The only way for us to be able to track this
down would be a reproducible case with valgrind. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2011-03-31 02:35 tilghman       Note Added: 0133193                          
======================================================================