Re: segfaults
Craig Main <[email protected]>
| Newsgroups | gmane.comp.python.db.pypgsql.user |
|---|---|
| Organization | ST Solutions |
| Message-ID | <[email protected]> |
On Wed, 2003-04-23 at 14:47, Gerhard Häring wrote: > 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.) > Good news (maybe) for the pypgsql team, I seem to have tracked the problem down to the "from mx import DateTime" line in the PgSQL.py file. Running the that line from the python shell segfaults. So it appears that the root cause of the segfaulting is not the pypgsql code. The line "from pyPgSQL import libpq" does not crash... Any ideas? I dont seem to find a mx-dev list anywhere? TIA Craig -- Craig Main RHCE ST Solutions Cell: 082-323-4670 Home Tel: 011-760-1900 AIM: SATuxman; ICQ: 75815570
signature.asc
(application/pgp-signature, 189 B)
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQA+qTXbJroSkVVrhL4RAjy0AKCR4Hn460rbwPgD8YLQlS+zVXBXkACeNN/Z J3O4H2faR0jiozN0sM3/2mU= =SEwz -----END PGP SIGNATURE-----