Re: [Bug-gnubg] Fwd: Bug#396445: gnubg: segfault adding match to postgres database

2006-11-10 Thread Christian Anthon
Hi Russ, could you tell us what the code looks like around the failing line | #5 0x005078f0 in PyGameStats (sc=0xd91380, fIsMatch=0, nMatchTo=7) | at gnubgmodule.c:1558 since I don't know what revision of gnubgmodule.c you have. In my version it says, PyObject* d =

Re: [Bug-gnubg] Fwd: Bug#396445: gnubg: segfault adding match to postgres database

2006-11-10 Thread Russ Allbery
Christian Anthon [EMAIL PROTECTED] writes: Hi Russ, could you tell us what the code looks like around the failing line | #5 0x005078f0 in PyGameStats (sc=0xd91380, fIsMatch=0, nMatchTo=7) | at gnubgmodule.c:1558 since I don't know what revision of gnubgmodule.c you have. In

[Bug-gnubg] Fwd: Bug#396445: gnubg: segfault adding match to postgres database

2006-11-09 Thread Russ Allbery
One more bug forwarded from Debian. I'm afraid that this segfault is deep enough in Python code that I don't really know what to look for. This segfault occurs on AMD64. Apparently the x86 package segfaults in other places. Here's the original report: | Package: gnubg | Version: