Comment 3 for bug 194788

Hi,

Tres Seaver schrieb:
> paul.brettschneider wrote:
>> ** Attachment added: "gdb backtraces"
>> http://launchpadlibrarian.net/12164156/zope_segfaults.txt
>
> 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/DebuggingWithGdb
>
> In particular, the gdb macros shipped with Python are useful for examing
> objects in the C stackframe.
>
>
> Tres.

Note: I'm currently tracking down some segfault as well. I discovered
one in psycopg. You might try using latest psycopg2 stable release
branch, it incorporates several segmentation fault fixes.

The other that I'm currently hunting is different from what you gave here.

Christian

--
gocept gmbh & co. kg - forsterstrasse 29 - 06112 halle (saale) - germany
www.gocept.com - <email address hidden> - phone +49 345 122 9889 7 -
fax +49 345 122 9889 1 - zope and plone consulting and development