[asterisk-bugs] [Asterisk 0015196]: [patch] Asterisk crash when using ODBC to insert record on table that does not exist
Asterisk Bug Tracker
noreply at bugs.digium.com
Tue May 26 13:46:14 CDT 2009
A NOTE has been added to this issue.
======================================================================
https://issues.asterisk.org/view.php?id=15196
======================================================================
Reported By: ajohnson
Assigned To: tilghman
======================================================================
Project: Asterisk
Issue ID: 15196
Category: Functions/func_odbc
Reproducibility: always
Severity: crash
Priority: normal
Status: assigned
Asterisk Version: 1.6.2.0-beta2
Regression: No
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Request Review:
======================================================================
Date Submitted: 2009-05-26 10:35 CDT
Last Modified: 2009-05-26 13:46 CDT
======================================================================
Summary: [patch] Asterisk crash when using ODBC to insert
record on table that does not exist
Description:
When using func_odbc to insert a record into a table that does not exist,
asterisk will crash after attempting to reconnect to the database. I have
not tested this in other error scenarios.
MySQL Server version: mysql-server.x86_64 5.0.45-7.el5
unixODBC.i386 2.2.11-7.1
unixODBC-devel.i386 2.2.11-7.1
func_odbc.conf
[SET]
prefix=DB
dsn=mysql
writesql = INSERT INTO asterisk.CallVariables (uid,name,value) VALUES
('${SQL_ESC(${ARG1})}','${SQL_ESC(${VAL1})}','${SQL_ESC(${VAL2})}')
writesql += ON DUPLICATE KEY UPDATE value='${SQL_ESC(${VAL2})}'
======================================================================
----------------------------------------------------------------------
(0105449) tilghman (administrator) - 2009-05-26 13:46
https://issues.asterisk.org/view.php?id=15196#c105449
----------------------------------------------------------------------
Okay, that gives me a better idea as to what is happening, although the
'why' is still unclear. Could you apply this new debugging patch, and run
'./configure --enable-dev-mode' before recompiling, please? This should
provide a backtrace into the code as to when the problem is actually
occurring and why (instead of only after the fact, when the crash occurs).
Issue History
Date Modified Username Field Change
======================================================================
2009-05-26 13:46 tilghman Note Added: 0105449
======================================================================
More information about the asterisk-bugs
mailing list