[unixODBC-support] Another segfault in libodbccr.so on x86_64

Nick Gorham nick.gorham at easysoft.com
Sat Dec 22 15:09:21 GMT 2007

Colin Snover wrote:

>Hello again. (What, so soon?)
>After resolving the first segfault that was occurring by using the CVS
>source, now that I have configured the proper TDS version I've stumbled
>upon another crash.
>I've had this crash occur in different places (as you can see below) but
>always within the same function. I've attached two backtraces. The first
>backtrace is conducted against a query that had been working when the
>TDS Version was at its default (4.2); the second backtrace is conducted
>against a query that would fail (SQLError 4004) when TDS Version was 4.2
>because of an NTEXT column.
>Currently, neither execution gets far enough to actually make it to the
>data query (the thing that used to fail with TDS Version 4.2) -- only
>the metadata stored procedure is called before unixODBC dies. Normally,
>there would be a second query to "SELECT TOP 1 * FROM <table>".
>I've also attached two gzipped Trace logs corresponding to each
>backtrace; hopefully they help shed more light on this.

I will take a look later.

Does it work when you don't use the cursor lib? or is that essential to 
what you are doing?

I could suggest trying another driver, but that is a bit biased of me :-)


More information about the unixODBC-support mailing list