[unixODBC-dev] Regarding SQLAllocate handle.

Nick Gorham nick.gorham at easysoft.com
Tue Aug 29 12:41:09 BST 2006


sidhartha.bardoloye at wipro.com wrote:

>Hi,
>
>
>
>We have an application which uses just one connection handle and for
>this connection we have a global statement handle. The application
>crashed while trying to allocate the statement handle and on debugging
>the core file with dbx utility we see the following:
>
>
>
>(dbx) where
>  [1] realfree(0xffbfc8a8, 0x1a31, 0x2008, 0x2008, 0xffbfc2d0, 0x0), at
>0xff046fc4
>  [2] _malloc_unlocked(0x5d0, 0x0, 0x220e4, 0xff0bc000, 0x0, 0x0), at
>0xff046a3c
>  [3] malloc(0x5d0, 0x1, 0x22174, 0xff0bc000, 0xff0c2f34, 0x117428), at
>0xff0467b4
>  [4] calloc(0x5d0, 0x0, 0x11c248, 0xffbfeaa0, 0xff24c518, 0x1fe), at
>0xff037428
>  [5] __alloc_stmt(0xff24c518, 0x1fe, 0x0, 0x0, 0x1987c0, 0xff273088),
>at 0xff2375a0
>  [6] __SQLAllocHandle(0x3, 0x1987b8, 0x1173d8, 0x0, 0x0, 0x0), at
>0xff209ec0
>  [7] SQLAllocHandle(0x3, 0x1987b8, 0x1173d8, 0x0, 0x0, 0x0), at
>0xff20a724
>  [8] ODBCAllocHandle(flag = 2), line 79 in
>"/l1/src/Dev_3_2/ODBCLibrary/ODBCFunctions.c"
>
>
>
>This is the first time we are seeing this kind of an issue and it
>happened in the production scenario. We are using easy soft drivers and
>Oracle Database for a long time (over 1 year) and are not able to
>replicate the problem.
>
>  
>
That sort of problem is normally due to corruption of the memory heap 
somewhere before the crash. Normally I would suggest using valgrind to 
see if that gives any mnore hints, but as its one of our drivers, if you 
have support, I would contact support at easysoft.com

-- 
Nick Gorham
Easysoft Limited
http://www.easysoft.com, http://www.unixODBC.org




More information about the unixODBC-dev mailing list