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

Asterisk Bug Tracker noreply at bugs.digium.com
Fri Feb 27 14:57:43 CST 2009


The following issue has been UPDATED. 
====================================================================== 
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:                     new
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:              
====================================================================== 
Date Submitted:             2009-02-26 13:12 CST
Last Modified:              2009-02-27 14:57 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


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

---------------------------------------------------------------------- 
 (0100910) alerios (reporter) - 2009-02-27 14:57
 http://bugs.digium.com/view.php?id=14563#c100910 
---------------------------------------------------------------------- 
Ok, now I'm using sqlite3_3.5.9, with the patch you say applied
(http://www.sqlite.org/cvstrac/chngview?cn=5016), and I'm still getting a
segfault, but this time the backtrace is a bit different:

Core was generated by `/usr/sbin/asterisk -F -g -vvv -p -g -U asterisk'.
Program terminated with signal 11, Segmentation fault.
http://bugs.digium.com/view.php?id=0  sqlite3_exec (db=0x0, 
    zSql=0x83ea978 "INSERT INTO cdr
(clid,src,dst,dcontext,channel,dstchannel,lastapp,lastdata,start,answer,end,duration,billsec,disposition,amaflags,accountcode,uniqueid,userfield,pbx,intrunk,outtrunk,dialout)
VALUES ('"..., xCallback=0, pArg=0x0, pzErrMsg=0xb5d0bbd8) at
sqlite3.c:60343
60343	  sqlite3_mutex_enter(db->mutex);
(gdb) backtrace 
http://bugs.digium.com/view.php?id=0  sqlite3_exec (db=0x0, 
    zSql=0x83ea978 "INSERT INTO cdr
(clid,src,dst,dcontext,channel,dstchannel,lastapp,lastdata,start,answer,end,duration,billsec,disposition,amaflags,accountcode,uniqueid,userfield,pbx,intrunk,outtrunk,dialout)
VALUES ('"..., xCallback=0, pArg=0x0, pzErrMsg=0xb5d0bbd8) at
sqlite3.c:60343
http://bugs.digium.com/view.php?id=1  0xb76c6e7f in sqlite3_log (cdr=0x8614818)
at cdr_sqlite3_custom.c:274
http://bugs.digium.com/view.php?id=2  0x08084186 in post_cdr (cdr=0x8614818) at
cdr.c:1021
http://bugs.digium.com/view.php?id=3  0x080843a8 in ast_cdr_detach
(cdr=0x8614818) at cdr.c:1217
http://bugs.digium.com/view.php?id=4  0x080b2b02 in ast_bridge_call
(chan=0x86540c0, peer=0x84ff450,
config=0xb5d0cd98)
    at features.c:2246
http://bugs.digium.com/view.php?id=5  0xb6061306 in dial_exec_full
(chan=0x86540c0, data=0xb5d0ef28,
peerflags=0xb5d0ce80, 
    continue_exec=0x0) at app_dial.c:1959
http://bugs.digium.com/view.php?id=6  0xb6066819 in dial_exec (chan=0x86540c0,
data=0xb5d0ef28) at
app_dial.c:2023
http://bugs.digium.com/view.php?id=7  0x080e6a39 in pbx_exec (c=0x86540c0,
app=0x837cd08, data=0xb5d0ef28)
at pbx.c:944
http://bugs.digium.com/view.php?id=8  0x080f26f1 in pbx_extension_helper
(c=0x86540c0, con=0x0, 
    context=0x8654248 "macro-dial-std-exten", exten=0x8654298 "s",
priority=21, label=0x0, 
    callerid=0x82ec908 "dsec=25", action=E_SPAWN, found=0xb5d11ef4,
combined_find_spawn=1)
    at pbx.c:3113
http://bugs.digium.com/view.php?id=9  0xb6057430 in _macro_exec (chan=0x86540c0,
data=<value optimized out>,
exclusive=0)
    at app_macro.c:295
http://bugs.digium.com/view.php?id=10 0x080e6a39 in pbx_exec (c=0x86540c0,
app=0x8532058, data=0xb5d13fb8)
at pbx.c:944
http://bugs.digium.com/view.php?id=11 0x080f26f1 in pbx_extension_helper
(c=0x86540c0, con=0x0, 
    context=0x8654248 "macro-dial-std-exten", exten=0x8654298 "s",
priority=4, label=0x0, 
    callerid=0x82ec908 "dsec=25", action=E_SPAWN, found=0xb5d163f8,
combined_find_spawn=1)
    at pbx.c:3113
http://bugs.digium.com/view.php?id=12 0x080f4d05 in __ast_pbx_run (c=0x86540c0)
at pbx.c:3606
http://bugs.digium.com/view.php?id=13 0x080f653e in pbx_thread (data=0x86540c0)
at pbx.c:3956
---Type <return> to continue, or q <return> to quit---
http://bugs.digium.com/view.php?id=14 0x081306b0 in dummy_start (data=0x85258b0)
at utils.c:917
http://bugs.digium.com/view.php?id=15 0xb7cd4240 in start_thread () from
/lib/tls/i686/cmov/libpthread.so.0
http://bugs.digium.com/view.php?id=16 0xb7db049e in clone () from
/lib/tls/i686/cmov/libc.so.6
(gdb) 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-02-27 14:57 alerios        Note Added: 0100910                          
2009-02-27 14:57 alerios        Status                   closed => new       
2009-02-27 14:57 alerios        Resolution               no change required =>
reopened
======================================================================




More information about the asterisk-bugs mailing list