The segfault appears to be occurring during Python garbage collection.
Debugging this is going to require more information, I'm afraid:
- Rebuild Python with debugging support ('./configure --with-pydebug').
- Rebuild the C-extension modules (PIL, PsycoPG).
- Check the libraries that your Python and the C extensions are
linked against (via 'ldd').
If nothing jumps out at you after doing this work, then you will likely
need to use 'gdb' to investigate some of the objects involved on the
stack of the setgaulting thread. See:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
paul.brettschneider wrote: launchpadlibrar ian.net/ 12164156/ zope_segfaults. txt
> ** Attachment added: "gdb backtraces"
> http://
The segfault appears to be occurring during Python garbage collection.
Debugging this is going to require more information, I'm afraid:
- Rebuild Python with debugging support ('./configure --with-pydebug').
- Rebuild the C-extension modules (PIL, PsycoPG).
- Check the libraries that your Python and the C extensions are
linked against (via 'ldd').
If nothing jumps out at you after doing this work, then you will likely
need to use 'gdb' to investigate some of the objects involved on the
stack of the setgaulting thread. See:
http:// wiki.python. org/moin/ DebuggingWithGd b
In particular, the gdb macros shipped with Python are useful for examing
objects in the C stackframe.
Tres. ======= ======= ======= ======= ======= ======= ======= ======= ==== palladion. com enigmail. mozdev. org
- --
=======
Tres Seaver +1 540-429-0999 <email address hidden>
Palladion Software "Excellence by Design" http://
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://
iD8DBQFHwF4/ +gerLs4ltQ4RAsF iAJ9dQTTaPnp27C igPrhmci6QfEC5x QCghFRP rJncMTMWY=
+Ut5wHThjSYV7/
=RrR4
-----END PGP SIGNATURE-----