FreeTDS Development Group

[Frediano Ziglio <freddy77 AT gmail.com>]

2018-06-27 18:37 GMT+01:00 Igor Korot <ikorot01 AT gmail.com>:
> Hi, ALL,
> This post is not directly related to the freeTDS, but I'm hoping that
> someone can help.
>
> I have a latest Sybase 16.0 version Development Edition installed on Linux.
> I also have a unixODBC installed.
>
> I'm trying to connect to the server using the default Sybase ODBC
> driver with the
> unixODBC isql program.
>
> Unfortunately I have a problem. The connection works, but then issuing
> the simple
> query, like "SELECT * FROM <my_table>;", where my table is locatedinside
> my local database (the one I created) segfaults.
> Trying to do the same with the Sybase demo database works fine.
>
> I didn't try to do anything with the freeTDS driver yet. I will probably do 
> that
> over the weekend.
>
> Does anybody here have Sybase 16 installed? Did you try ODBC connection
> to the server?
>
> Thank you.
>
> P.S.: Software versions:
> 1> select @@version
> 2> go
>
> ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
> Adaptive Server Enterprise/16.0 SP02 PL02/EBF 25320 SMP/P/x86_64/Enterprise 
> Lin
> ux/ase160sp02plx/2492/64-bit/FBO/Sat Nov 21 04:05:39 2015
>
> (1 row affected)
> 1> exit
>
> [/code]
>
> [code]
>
> [ebuild U ] dev-db/unixODBC-2.3.5-r1::gentoo [2.3.2-r1::gentoo]
> USE="minimal unicode -odbcmanual -static-libs" ABI_X86="32 (64)
> (-x32)" 1,596 KiB
>
> [/code]
>
> The current version of unixODBC is 2.3.2-r1 from gentoo repository.

Sounds a silly question: are unixODBC and Sybase driver using the
same ABI? Yes, sounds crazy but unixODBC can be compiled with
slightly different ABIs on 64 bit.
You could enable ODBC tracing to see the last call producing the fault.
Maybe program is using wide functions and this is the issue?

Frediano