[unixODBC-support] core dump in libodbccr.so on HP iA64

Cherie Soleil sunf2002 at gmail.com
Tue Nov 13 08:15:53 GMT 2007

When we use unixodbc driver manager on HP IA64 we encountered one
problem. Would you please help me to have a check.

We use unixodbc driver manager to load DB2 driver libdb2o(DB2
v9.1.0.3","s070719","U811592","Fixpack 3") to connect to db2. When we
connect to db2 on os390 or as400 and do some kinds of cursor operation
libodbc.so will call libodbccr.so even we set SQL_CUR_USE_DRIVER and
met a core dump in libodbccr.so. ( If connect to db2 on NT or Unix
it's ok. If use unixodbc driver manager to connect to datadirect
driver libodbccr.so won't be called for all kinds of db2 database.)

core dump information when using unixodbc build by aCC:

#0  0xc0000000002adee0:0 in memmove+0x40 () from /lib/hpux64/libc.so.1
(gdb) where
#0  0xc0000000002adee0:0 in memmove+0x40 () from /lib/hpux64/libc.so.1
#1  0xc0000000071c6b50:0 in fetch_row () at SQLExtendedFetch.c:277
#2  0xc0000000071c7610:0 in fetch_rowset () at SQLExtendedFetch.c:464
#3  0xc0000000071c7ca0:0 in do_fetch_scroll () at SQLExtendedFetch.c:595
#4  0xc0000000071c9400:0 in CLFetch () at SQLFetch.c:87
#5  0xc000000013ba6130:0 in SQLFetch () at SQLFetch.c:293
#6  0xc000000013a92020:0 in odbcRowSetResult::fetchRow (
    this=0x9fffffffef380a00) at odbcrst.cpp:1067  > our code

core dump information when using unixodbc build by gcc:

#0  0xc0000000002adee0:0 in memmove+0x40 () from /usr/lib/hpux64/libc.so.1
#1  0xc00000000c5e1200:0 in fetch_row+0xe10 ()
   from /usr/u/fsun/unixodbc/lib/libodbccr.so.1
#2  0xc00000000c5e20d0:0 in fetch_rowset+0xf0 ()
   from /usr/u/fsun/unixodbc/lib/libodbccr.so.1
#3  0xc00000000c5e2af0:0 in do_fetch_scroll+0x720 ()
   from /usr/u/fsun/unixodbc/lib/libodbccr.so.1
#4  0xc00000000c5e4db0:0 in CLFetch+0x2c0 ()
   from /usr/u/fsun/unixodbc/lib/libodbccr.so.1
#5  0xc000000017dc11e0:0 in SQLFetch+0xd40 ()
   from /usr/u/fsun/unixodbc/lib/libodbc.so.1.0
#6  0xc0000000126c9fc0:0 in odbcRowSetResult::fetchRow (
    this=0x9fffffffef49ca00) at odbcrst.cpp:1067

Do you have any suggestion for such problem? Thank you very much.

More information about the unixODBC-support mailing list