Re: need help with some bugs in python-mysqldb

2004-09-21 Thread Matthias Klose 
could you try rebuilding/reinstalling the libapache-mod-python package?

Jonas Meurer writes:
 On 21/09/2004 Alexandre wrote:
  On Tue, Sep 21, 2004 at 04:09:03PM +0200, Jonas Meurer wrote:
   it's a problem with libapache-mod-python, it segfaults at using
   MySQL-Python. see #270555 for more information.
  
  Would you happen to have a post mortem analysis of apache available, in
  order to see what precisely causes the segfault ?
 
 all i can tell you, is what error.log from apache reports:
 [Tue Sep 21 18:55:41 2004] [notice] mod_python: (Re)importing testapp from 
 None
 [Tue Sep 21 18:55:42 2004] [notice] child pid 15196 exit signal Segmentation 
 fault (11)
 
 the process with pid 15196 doesn't exist, if i ps for it.
 
 i don't use libapache-mod-python myself, but there are at least 4 people
 using python-mysqldb who reported the problem to me, and i'm pretty good
 able to reproduce the bug.
 
 if you're interested in debugging, i can provide the testapp.py and a
 corresponding test.sql to reproduce the bug.
 
 bye
  jonas

need help with some bugs in python-mysqldb

2004-09-21 Thread Jonas Meurer 
hello,

i need some help with a bug in python-mysqldb which i am the maintainer
for. the two reports that explain the bug are #270555 and #270570.

it's a problem with libapache-mod-python, it segfaults at using
MySQL-Python. see #270555 for more information.

the strange thing here is, that this happens only when compiling with
mysql 4.0.21 (libmysqlclient-dev in debian/unstable). if i use mysql
3.23.56 (libmysqlclient10-dev in debian/unstable), the problem doesn't
occur.
i've uploaded a new release, built with libmysqlclient10, to unstable
today to workaround this bug, but generally mysql 4.0 is highly
recommented and much more supported by most recent MySQL-Python.

it doesn't matter which mysql server version you run when you connect
to it with a MySQL-Python, the only important thing is whether you build
it with libmysqlclient 3.23.56 or 4.0.21.

upstream is pretty ignorant about this issue, so all i can do is find
the bug myself, but i'm afraid that i'll fail.

does anybody have suggestions how to go on?

bye
 jonas