Summary:	ASTERISK-07769: Segfault when using an argument for the LIMIT value
Reporter:	Leif Madsen (lmadsen)	Labels:
Date Opened:	2006-09-18 21:18:22	Date Closed:	2011-06-07 14:01:07
Priority:	Critical	Regression?	No
Status:	Closed/Complete	Components:	Functions/func_odbc
Versions:		Frequency of Occurrence
Related Issues:
Environment:		Attachments:	( 0) backtrace-func_odbc-hash.txt
Description:	func_odbc.conf: read=SELECT tech, member_id FROM ast_queue_members WHERE pbx_queues_id = '${ARG1}' LIMIT '${ARG2}' extensions.conf: exten => rrmemory,n,Set(HASH(HUNT_${X})=${HUNT_MEMBERS(${Q_ID},${LIMIT})}) When using the following lines in Asterisk, func_odbc HASH function segfaults. When using a LIMIT 0 (no ${ARG2}) it works fine Backtrace attached.
Comments:	By: Leif Madsen (lmadsen) 2006-09-18 22:49:54 Real issue is that the example I had found for controlling what rows are returned was actually incorrect. This function only crashed when I added a comma after the LIMIT value. I'll leave it up to Corydon to re-open this issue if he wishes to change something. FYI: this is with the 1.2 version of func_odbc By: Leif Madsen (lmadsen) 2006-09-18 22:50:24 Bah -- I'm a nub. Now closed.