[unixODBC-support] Core dump issue from UnixODBC on AIX platform

Nick Gorham nick.gorham at easysoft.com
Mon Nov 5 16:34:33 GMT 2007

Hassan Shaik wrote:

>Hi Nick,
>I need few more clarifications:
>1. I extracted UnixODBC2.2.13pre source and the source code in
>__handles.c looks similar. Will there be any impact on this problem from
>code changes in other files?
>2. Adding "Threading = 0" to odbcinst.ini file is just a suggestion, and
>may not solve this issue, right?
>3. If the above two can't solve this problem, we need to analyze the
>current code. I checked the Makefile under the directory where I built
>UnixODBC2.2.12. The flag HAVE_LIBTHREAD is set there. So, following code
>is active in __handles.c, 
Build the entire thing, don't just pull individual files. Part of the 
reason for building 2.2.13 is that it does hav thread related fixes, and 
the other part is if I look at the problem I will be starting with that 

>But mutex_entry( &mutex_lists ) and mutex_exit( &mutex_lists ) calls are
>used at start and end of these functions. I am wondering how come str
>can become NULL suddenly, as we already validating for it in while loop
>(using while( ptr )). 
>Sorry, if I am troubling you with many questions.
>Please clarify on this.
Well, I guess if we knew this we would know what the problem is.

How many threads does your app use, how long does it run before failing, 
does it always fail at the same place?

I ask these question to ge a feeling for how much effort would be 
required to fix the problem.

Have you tried any code validation tools? Maybe IBM's Purify?


More information about the unixODBC-support mailing list