[unixODBC-support] core dump in libodbccr.so on HP iA64
sunf2002 at gmail.com
Tue Nov 13 10:16:56 GMT 2007
Can you tell me how to get unixodbc trace.
If I set
in odbc.ini the trace file won't be created. In our application we
use dlopen(libodbc.so) to use the API interface. If [ODBC] entry must
be put in odbcinst.ini ? I set ODBCINI as my odbc.ini ,how can I
generate one odbcinst.ini and make it take effect?
On Nov 13, 2007 6:07 PM, Nick Gorham <nick.gorham at easysoft.com> wrote:
> Cherie Soleil wrote:
> >Hi Nick
> >I am using unixODBC-2.2.12.
> >Here's the information in my odbc.ini
> >I add the UDB39081 in db2 instance as database alias.
> >If I use the 32bit unixodbc on linux and solaris, when I connect to
> >db2 on os390 and as400 it will call libodbccr.so samely but no core
> >dump. And when connect to db2 on NT and Unix libodbccr.so won't be
> >As I said libodbccr.so won't be called when use unixodbc to load
> >datadirect driver no matter connect to db2 os390 or as400.
> Ok, it may be that there is a 64 bit issue with the cursor lib. I will
> take a look at that.
> What I don;t understand is how or why its using the cursor lib if
> SQL_CUR_USE_DRIVER is set.
> Could you send a ODBC trace of the app connecting and up to the point of
> it failing?
> Nick Gorham
> Easysoft Limited
> http://www.easysoft.com, http://www.unixODBC.org
> unixODBC-support mailing list
> unixODBC-support at easysoft.com
More information about the unixODBC-support