Re: segfaults

Craig Main wrote:
> On Tue, 2003-04-22 at 16:16, Gerhard Häring wrote:
> 
> 
>>Ouch. This isn't useful :-(
>>
>>To debug these kind of crashes we'll need to add diagnostic output to 
>>the C sources. Could you please apply the attached patch to 
>>libpqmodule.c (the patch is against pyPgSQL 2.3) and post the output of 
>>a "from pyPgSQL import libpq" ?
>>
> 
> 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 
> 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

Ok, so it doesn't actually die in the module initialization phase of the 
C module. Could you please add print statements into 
pyPgSQL/libpq/__init__.py so to show where it dies there?

(This sounds like an obscure bug to me, perhaps caused by too agressive 
compiler settings that trigger a gcc bug.)

-- Gerhard


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf