Re: Segentation faults when connecting to SQL Server 2000
Dave Cole <[email protected]>
| Newsgroups | gmane.comp.python.sybase |
|---|---|
| Message-ID | <[email protected]> |
>>>>> "Kevin" == Kevin Jacobs <[email protected]> writes: Kevin> On 9 Sep 2002, Peter Hopfgartner wrote: >> I'm trying to use the Sybase module from a Debian Linux 3.0 system >> (Python 2.1.3, FreeTDS 0.53). >> >> I've set up some Python code in order to create ASCII file >> containing the database scheme, functions and stored >> procedures. The code runs fine when connecting through ODBC from a >> Windows computer. It crashes when connecting from the Linux client, >> as soon as the 2nd query is run. >> >> Has there already been some work done on it, both from the FreeTDS >> side (version 0.60rc1 came out these days, should I install it?) >> and the Sybase module side. Can I help in debugging the problem? Kevin> All I can suggest is that you use the _very_ lastest FreeTDS Kevin> library. The last released version had some rather nasty bugs Kevin> in it. >> As soon as I have again the chance to connect to the SQL Server >> (it's at a customers place) I will paste you the exact message >> (something about threads and relesing a lock that has not been >> set). Kevin> Ah! I've run into this myself. I'll dig up my patches that Kevin> re-work the Sybase module locking code that fixes it (though Kevin> I'm not sure if I'm just working around errors in the FreeTDS Kevin> LibCT implementation or unsafe assumptions that David Cole made Kevin> about Sybase's implementation). I am very keen to get the module working with FreeTDS. I think the future of the module is largely tied to the success of FreeTDS. - Dave -- http://www.object-craft.com.au