FreeTDS Development Group

[Matthew Bartholomew <Matt AT Mastrapasqua.com>]

It seems that my problem was with the unixODBC rpms.  I went back down to
unixODBC-2.1.1-3 which also gave me the same seg fault issue.  I've
downloaded so many rpms this week, so I'm not real sure where I got that rpm
from (either from rpmfind.net or redhat.com).  

Anyways, I upgraded to unixODBC-2.2.0-5 (from rpmfind.net) and it solved my
seg fault issue.  

In summary, I believe that the seg fault was caused by something in
unixODBC-2.1.1-3 and unixODBC-2.2.2-3.  Sorry I'm not better at tracking
these things down in order to contribute more to community...

Thanks
Matt



-----Original Message-----
From: Matthew Bartholomew 
Sent: Tuesday, December 03, 2002 5:20 PM
To: 'freetds AT lists.ibiblio.org.'
Cc: 'freeodbc AT as220.org'; 'dbi-users AT perl.org'; 'dbi-dev AT perl.org';
'unixodbc-dev AT unixodbc.org'
Subject: RE: unixODBC and isql seg fault

Thanks for the help Nick...

If anyone from the freetds arena can add some guidance...that would be
wonderful.

Here is one last odd quirk that I haven't mentioned....I am able to connect
to the MS SQL 2k server and query without issue via php 4.2.2!  The seg
fault occurs when running isql from a bash shell and any perl scripts that
use DBI->connect("DBI:ODBC:DSN",'USERname', 'PASS')


Per Nick Gorham, here are my gdb results:
---
(gdb) r -v SQL
Starting program: /usr/bin/isql -v SQL
[New Thread 8192 (LWP 14857)]
        
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 8192 (LWP 14857)]
0x4007b8df in uodbc_get_stats () from /usr/lib/libodbc.so.1
(gdb) quit
---

I have no idea what the above message means, so if anyone can shed some
light...I would appreciate it.  

For users on the Freetds list, please see the bottom of this email for the
start of this email thread.  The issue is a basic seg fault when using isql
to connect to a MS SQL 2k server.  I have freetds0.60, unixODBC 2.2.2-3, and
Sybase 11.9 family of rpms installed on a redhat 7.2 linux.  Using perl
5.8.0 with DBI and DBD::ODBC (most up to date versions that cpan will allow
on 12/03/02).

It should be noted that I have another linux box talking with a MS SQL 2K
server using freetds-0.53-1, unixODBC-2.1.1-1, perl-5.6.1-26.72.3.  That
configuration works flawlessly...so others may want to wait a bit longer
until they upgrade to those packages.

Thanks,
Matt


> Hello again,
> 
> I was able to connect to mysql via isql (I'm having a difficult time 
> with postgresql).  Do you think that puts unixODBC in the clear and I 
> should look around at other packages as the perpetrators of this seg 
> fault?  Or does postgresql hold a significance that I'm not getting?

No, its going to be a freetds thing I suspect. I would try running isql 
under gdb

gdb isql
r -v dsnname

and see where it fails

I would try asking on the freetds lists.

BTW. I have snipped the reply to list.

Nick



-----Original Message-----
From: Matthew Bartholomew 
Sent: Tuesday, December 03, 2002 4:23 PM
To: 'Nick Gorham'
Cc: 'freeodbc AT as220.org'; 'dbi-users AT perl.org'; 'dbi-dev AT perl.org';
'unixodbc-dev AT unixodbc.org'
Subject: RE: unixODBC

Hello again,

I was able to connect to mysql via isql (I'm having a difficult time with
postgresql).  Do you think that puts unixODBC in the clear and I should look
around at other packages as the perpetrators of this seg fault?  Or does
postgresql hold a significance that I'm not getting? 

Since then, I've re-installed freetds 0.60 and the Sybase 11.9.2-1 family of
rpms, but same results:

[root@ns3 sybase]# isql SQL -v wibble
Segmentation fault 

Cheers,
Matt


-----Original Message-----
From: Nick Gorham [mailto:nick AT lurcher.org] 
Sent: Tuesday, December 03, 2002 2:27 PM
To: Matt AT Mastrapasqua.com
Subject: unixODBC

Hi,

I would try isql first, there are several reasons you may get a seg 
fault in ODBCConfig all you need is mismatched QT libs.

Try and get a postgres connection working.

Nick



---------------------------------------------------------------------------

For those on the freetds list...here is the start of this thread:

From: Matthew Bartholomew 
Sent: Tuesday, December 03, 2002 4:23 PM
To: 'Nick Gorham'
Cc: 'freeodbc AT as220.org'; 'dbi-users AT perl.org'; 'dbi-dev AT perl.org';
'unixodbc-dev AT unixodbc.org'
Subject: RE: unixODBC


Not sure what to do from here...any advice would be great.  Thanks...
-Matt

[root@ns3 root]# isql -v
Segmentation fault
[root@ns3 build]# isql -b
Segmentation fault
[root@ns3 build]# isql -c
Segmentation fault
[root@ns3 build]# isql -w
Segmentation fault
[root@ns3 build]# isql -mn
Segmentation fault
....you get the idea...isql seg faults on most every command. --version is
the only one that doesn't seg fault.  I upgrade to unixODBC 2.2.2 in hopes
of fixing this, but no avail.  

Also, I've tried to recompile DBD::ODBC but make test fails...probably
because unixodbc is seg faulting when called (see below for that error..and
it should be noted that I removed the s from the makefile).


Here is what I am running:
RedHat 7.2 kernel 2.4.7-10
perl 5.8
unixODBC-2.2.2-3
freetds-0.60-1
glibc-2.2.93-5
DBD::ODBC 0.43

DBI is up to date (Database was generated on Mon, 02 Dec 2002 11:54:12 GMT 
--- I don't know the version #)

ODBCHOME=/usr
and the correct DSN settings are in my environment


-------------- odbcinst.ini ------------------
[SQL]
Description             = v0.52 with protocol v4.2
Driver          = /usr/lib/libtdsodbc.so
FileUsage               = 2

[TXT]
Description             = Text file driver
Driver          = /usr/lib/libodbctxt.so
Setup           = /usr/lib/libodbctxtS.so
FileUsage               = 2

[PostgreSQL]
Description             = PostgreSQL driver
Driver          = /usr/lib/libodbpsql.so
Setup           = /usr/lib/libodbpsqlS.so
FileUsage               = 2
----------------------------------------------



[root@ns3 DBD-ODBC-0.43]#   make test TEST_VERBOSE=1
PERL_DL_NONLAZY=1 /usr/local/bin/perl "-MExtUtils::Command::MM" "-e"
"test_harness(1, 'blib/lib', 'blib/arch')" t/*.t
t/01base......1..5
ok 1
ok 2
ok 3
ok 4
ok 5
ok
t/02simple....1..17
ok 1
 Test 2: connecting to the database
dubious
        Test returned status 0 (wstat 11, 0xb)
DIED. FAILED tests 2-17
        Failed 16/17 tests, 5.88% okay
t/03dbatt.....1..9
ok 1
dubious
        Test returned status 0 (wstat 11, 0xb)
DIED. FAILED tests 2-9
        Failed 8/9 tests, 11.11% okay
t/05meth......1..6
ok 1
dubious
        Test returned status 0 (wstat 11, 0xb)
DIED. FAILED tests 2-6
        Failed 5/6 tests, 16.67% okay
t/07bind......1..9
ok 1
 Test 2: connecting to the database
dubious
        Test returned status 0 (wstat 11, 0xb)
DIED. FAILED tests 2-9
        Failed 8/9 tests, 11.11% okay
t/08bind2.....dubious
        Test returned status 0 (wstat 11, 0xb)
t/09multi.....dubious
        Test returned status 0 (wstat 11, 0xb)
Failed Test  Stat Wstat Total Fail  Failed  List of Failed
----------------------------------------------------------------------------
---
t/02simple.t    0    11    17   16  94.12%  2-17
t/03dbatt.t     0    11     9    8  88.89%  2-9
t/05meth.t      0    11     6    5  83.33%  2-6
t/07bind.t      0    11     9    8  88.89%  2-9
t/08bind2.t     0    11    ??   ??       %  ??
t/09multi.t     0    11    ??   ??       %  ??
Failed 6/7 test scripts, 14.29% okay. 37/46 subtests failed, 19.57% okay.
make: *** [test_dynamic] Error 2