[unixODBC-support] Crash in logging

Wang, Alan alan.wang at sap.com
Wed Nov 30 05:49:43 GMT 2005

Hi all,

I encountered an strange problem today! When I tried to run an
application on RedFlag Desktop 4.1(an linux distribution from China),
Which bundled the unixODBC 2.2.8-, I got an core dump :-(, here
is the stack trace :

#0  0x40b90d18 in write () from /lib/i686/libc.so.6
#1  0x40bf5940 in __DTOR_END__ () from /lib/i686/libc.so.6
#2  0x40b2bae2 in _IO_new_file_write () from /lib/i686/libc.so.6
#3  0x40b2aa6e in new_do_write () from /lib/i686/libc.so.6
#4  0x40b2aa06 in _IO_new_do_write () from /lib/i686/libc.so.6
#5  0x40b2a2c8 in _IO_new_file_close_it () from /lib/i686/libc.so.6
#6  0x40b201b8 in fclose@@GLIBC_2.1 () from /lib/i686/libc.so.6
#7  0x4195066a in dm_log_write (function_name=0x41965d4e "__handles.c",
line=421, type=0, severity=0,
    message=0x9c866d8 "\n\t\tExit:[SQL_SUCCESS]\n\t\t\tEnvironment =
0x9c866d0") at __info.c:5598
#8  0x419462f6 in __alloc_env () at __handles.c:420
#9  0x4190dac7 in __SQLAllocHandle (handle_type=-27, input_handle=0x0,
output_handle=0x9bfbe24, requested_version=2) at SQLAllocHandle.c:281
#10 0x4190d9e7 in SQLAllocEnv (environment_handle=0xffffffe5) at

(NOTE : I've enabled the odbc trace in odbcinst.ini in the above case,
if I disable the odbc trace, all are OK!)

Thanks in advance!


More information about the unixODBC-support mailing list