From: Craig M. <cr...@th...> - 2003-04-23 06:01:24
|
On Tue, 2003-04-22 at 16:16, Gerhard H=E4ring wrote: > Ouch. This isn't useful :-( >=20 > To debug these kind of crashes we'll need to add diagnostic output to=20 > the C sources. Could you please apply the attached patch to=20 > libpqmodule.c (the patch is against pyPgSQL 2.3) and post the output of=20 > a "from pyPgSQL import libpq" ? >=20 With the patch compiled in, and using a this file test.py containing: #!/usr/bin/python from pyPgSQL import libpq I get this output: laptop test # python test.py=20 FILE: libpqmodule.c, LINE: 950 FILE: libpqmodule.c, LINE: 952 FILE: libpqmodule.c, LINE: 954 FILE: libpqmodule.c, LINE: 956 FILE: libpqmodule.c, LINE: 963 FILE: libpqmodule.c, LINE: 965 FILE: libpqmodule.c, LINE: 967 FILE: libpqmodule.c, LINE: 969 FILE: libpqmodule.c, LINE: 971 FILE: libpqmodule.c, LINE: 973 FILE: libpqmodule.c, LINE: 975 FILE: libpqmodule.c, LINE: 980 FILE: libpqmodule.c, LINE: 982 FILE: libpqmodule.c, LINE: 1101 FILE: libpqmodule.c, LINE: 1162 Regards Craig --=20 Craig Main RHCE ST Solutions Cell: 082-323-4670 Home Tel: 011-760-1900 AIM: SATuxman; ICQ: 75815570 |