[asterisk-bugs] [Asterisk 0014563]: Segmentation fault caused by sqlite3_log

[Asterisk Bug Tracker]

The following issue has been CLOSED 
====================================================================== 
http://bugs.digium.com/view.php?id=14563 
====================================================================== 
Reported By:                alerios
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   14563
Category:                   CDR/cdr_sqlite3_custom
Reproducibility:            always
Severity:                   crash
Priority:                   normal
Status:                     closed
Asterisk Version:           1.6.0.5 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
Resolution:                 no change required
Fixed in Version:           
====================================================================== 
Date Submitted:             2009-02-26 13:12 CST
Last Modified:              2009-02-26 13:55 CST
====================================================================== 
Summary:                    Segmentation fault caused by sqlite3_log
Description: 
Asterisk 1.6.0.5 randomly crashes, apparently because of the
cdr_sqlite3_custom module.

I'm using debian etch, with these versions of libsqlite:

ii  libsqlite3-0         3.3.8-1.1            SQLite 3 shared library
ii  libsqlite3-dev       3.3.8-1.1            SQLite 3 development files


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

---------------------------------------------------------------------- 
 (0100837) tilghman (administrator) - 2009-02-26 13:55
 http://bugs.digium.com/view.php?id=14563#c100837 
---------------------------------------------------------------------- 
This is a known issue in SQLite.  Please see
http://www.sqlite.org/cvstrac/tktview?tn=3059 for the fixed version. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-02-26 13:55 tilghman       Note Added: 0100837                          
2009-02-26 13:55 tilghman       Status                   new => closed       
2009-02-26 13:55 tilghman       Resolution               open => no change
required
======================================================================