[asterisk-bugs] [Asterisk 0013784]: segfault in res_odbc.c when rtupdate=yes in sip.conf with MS-SQL ODBC

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=13784 
====================================================================== 
Reported By:                jjotham
Assigned To:                Corydon76
====================================================================== 
Project:                    Asterisk
Issue ID:                   13784
Category:                   Channels/chan_sip/Registration
Reproducibility:            sometimes
Severity:                   crash
Priority:                   normal
Status:                     feedback
Asterisk Version:           1.6.0 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             2008-10-25 23:25 CDT
Last Modified:              2008-10-27 18:27 CDT
====================================================================== 
Summary:                    segfault in res_odbc.c when rtupdate=yes in sip.conf
with MS-SQL ODBC
Description: 
system registers and updates users inot MS-SQL table sippeers, sipusers
using unixODBC and FreeTDS 0.64
whenever rtupdate is set to yes asterisk crashes after updating several
SIP peers registrations. Crash occurs on call to function SQLFreeHandle in
res_odbc.c
Tested Crash in versions 1.6.01, 1.4.21 and 1.2.30.2

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

---------------------------------------------------------------------- 
 (0094321) Corydon76 (administrator) - 2008-10-27 18:27
 http://bugs.digium.com/view.php?id=13784#c94321 
---------------------------------------------------------------------- 
The only thing that I can think of that would even be tangentially our
issue would be some memory error that could be tracked down with valgrind. 
Otherwise, we're looking at a bug in FreeTDS.

Can you repeat the steps necessary to cause this bug while Valgrind is
running, then upload the resulting valgrind output? 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2008-10-27 18:27 Corydon76      Note Added: 0094321                          
======================================================================