[asterisk-bugs] [Asterisk 0015889]: crash because of invalid cdr->dst string

[Asterisk Bug Tracker]

The following issue requires your FEEDBACK. 
====================================================================== 
https://issues.asterisk.org/view.php?id=15889 
====================================================================== 
Reported By:                fhackenberger
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   15889
Category:                   CDR/General
Reproducibility:            random
Severity:                   crash
Priority:                   normal
Status:                     feedback
Asterisk Version:           SVN 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): 1.6.1 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-09-14 06:34 CDT
Last Modified:              2009-09-15 12:06 CDT
====================================================================== 
Summary:                    crash because of invalid cdr->dst string
Description: 
The actual crash is due to a race condition with SQLAllocHandle. Asterisk
reconnects to the DB if executing a statement fails. If, at the same time,
another thread tries to execute a statement, we have a crash. Threads 1, 3
in the attached backtrace. However, a failing DB statement during normal
operation should not happen in the first place. The statement which fails
is an INSERT into the asterisk cdr. The reason for aborting the statement
seems to be the field 'dst' which is set to:
(gdb) print /x cdr.dst
$3 = {0xff, 0x0, 0x32, 0x37, 0x0 <repeats 76 times>}
cdr.dst is set to chan.exten when the cdr struct is initialised.
chan.exten in turn is set to "" when the channel struct is initialised. I
cannot see a way for it to be uninitialised.
====================================================================== 

---------------------------------------------------------------------- 
 (0110691) lmadsen (administrator) - 2009-09-15 12:06
 https://issues.asterisk.org/view.php?id=15889#c110691 
---------------------------------------------------------------------- 
I believe the backtrace would be more useful to the developers if you're
able to reproduce this issue and obtain a backtrace when DONT_OPTIMIZE is
enabled in the Compiler Flags section of menuselect.

More information is available in doc/backtraces.txt

Thanks! 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-09-15 12:06 lmadsen        Note Added: 0110691                          
2009-09-15 12:06 lmadsen        Status                   new => feedback     
======================================================================