[asterisk-bugs] [Asterisk 0014716]: Crash using func_odbc

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=14716 
====================================================================== 
Reported By:                sum
Assigned To:                tilghman
====================================================================== 
Project:                    Asterisk
Issue ID:                   14716
Category:                   Functions/func_odbc
Reproducibility:            have not tried
Severity:                   crash
Priority:                   normal
Status:                     confirmed
Asterisk Version:           1.6.2.0-beta1 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-03-21 13:33 CDT
Last Modified:              2009-03-26 11:21 CDT
====================================================================== 
Summary:                    Crash using func_odbc
Description: 

Crash using func_odbc

1) with don't optimize it doesn't crash
2) with debug malloc realtime stop working with this error:

Connected to Asterisk 1.6.2.0-beta1 currently running on localhost (pid =
16736)
Verbosity was 3 and is now 4
failed to extend from 16 to 63
failed to extend from 16 to 43
[Mar 21 00:31:07] WARNING[16755]: res_config_mysql.c:369 realtime_mysql:
MySQL RealTime: Failed to query database: Query was empty
failed to extend from 16 to 63
[Mar 21 00:31:07] WARNING[16755]: res_config_mysql.c:369 realtime_mysql:
MySQL RealTime: Failed to query database: Query was empty
[Mar 21 00:31:07] NOTICE[16755]: chan_sip.c:20367 handle_request_register:
Registration from '"1001"<sip:1001 at 192.168.175.133>' failed for
'192.168.175.1' - No matching peer found


Tell me if you need valgrind file of the run without crashing, or any
other info.

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

---------------------------------------------------------------------- 
 (0102242) tilghman (administrator) - 2009-03-26 11:21
 http://bugs.digium.com/view.php?id=14716#c102242 
---------------------------------------------------------------------- 
That backtrace means you have memory corruption.  Valgrind is the normal
tool for tracking down corruption, and it is very normal for valgrind to
prevent crashes, as it is intercepting memory accesses and evaluating them
for correctness.  Just because two different people running valgrind see
that valgrind prevents the crash does NOT mean the crashes are related. 
Please don't make managing this issue more complicated than it needs to be
by drawing unfounded conclusions and expecting the bug marshals to follow
that red herring. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-03-26 11:21 tilghman       Note Added: 0102242                          
======================================================================