[asterisk-bugs] [Asterisk 0014286]: Crash on failure to execute SQL

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=14286 
====================================================================== 
Reported By:                darren1713
Assigned To:                Corydon76
====================================================================== 
Project:                    Asterisk
Issue ID:                   14286
Category:                   Resources/res_odbc
Reproducibility:            have not tried
Severity:                   minor
Priority:                   normal
Status:                     assigned
Asterisk Version:           1.4.22 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-01-20 12:58 CST
Last Modified:              2009-01-22 00:00 CST
====================================================================== 
Summary:                    Crash on failure to execute SQL
Description: 
* crashes when there is a SQL execute error.

I have attached a valgrind stack of the error. It is impossible to
reproduce in gdb because this error causes corrupted memory, which destroys
the stack in gdb.

In any case, the unixODBC code is very difficult to get a heads up on, but
I *think* that you cannot free the stmt if there was an error. I cannot
find any sample code to confirm this though...

Version is actually 1.4.22.1


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

---------------------------------------------------------------------- 
 (0098409) Corydon76 (administrator) - 2009-01-22 00:00
 http://bugs.digium.com/view.php?id=14286#c98409 
---------------------------------------------------------------------- 
I think it's clear that you've stumbled upon a bug in FreeTDS and you
should report this valgrind output to that project. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-01-22 00:00 Corydon76      Note Added: 0098409                          
======================================================================