Re: [python-sybase] Segentation faults when connecting to SQL Server 2000

[Harri P. <har...@tr...>]

On Tuesday 10 September 2002 10:18, hopfgartner wrote:
>
> Here we go:
>
> Traceback (most recent call last):
>   File "sqlDumpTbl.py", line 143, in ?
>     dump.dump()
>   File "sqlDump.py", line 64, in dump
>     obj_text =3D self.get_obj_definition(sp[0])
>   File "sqlDumpTbl.py", line 31, in get_obj_definition
>     self.sql_cursor.execute('SELECT name FROM sysobjects
> WHERE id =3D ' +
>   File "/usr/lib/python2.1/site-packages/Sybase.py", line
> 346, in execute
>     self._unlock()
>   File "/usr/lib/python2.1/site-packages/Sybase.py", line
> 259, in _unlock
>     self._owner._lock.release()
>   File "/usr/lib/python2.1/threading.py", line 101, in
> release
>     assert self.__owner is me, "release() of un-acquire()d
> lock"
> AssertionError: release() of un-acquire()d lock
>

I saw exactly the same thing.   If you feel adventurous you can apply the=
=20
quick and dirty patch I have attached to effectively remove the threading=
=20
support which I suspect you are not using anyway.

Note that the patch is in no way cleaned to be final, it just works for m=
e.

Just copy the Sybase.py from /usr/lib/python2.2/site-packages/Sybase.py
to your test script directory, and run:

patch < Sybase.py.test-patch

Then your script has a chance of passing this hurdle...

-Harri