[Zope-Coders] Zope 2.5 instability problems

[Martijn Faassen]

Tim Peters wrote:
> [Martijn Faassen]
> > Some more info on this, running Zope from gdb to see where it crashes.
> > Unfortunately I suspect that the C traceback isn't too useful, as I
> > suspect the corruption happens earlier somewhere, triggering the crash
> > later..
> >
> > Here's the top of one gdb 'bt':
> >
> > #0  0x400505bc in PyTuple_New () from /usr/lib/libpython2.1.so.0.0
> > #1  0x40050bfd in PyTuple_SetItem () from /usr/lib/libpython2.1.so.0.0
> > #2  0x40033b5d in PySequence_GetSlice () from usr/lib/libpython2.1.so.0.0
> > #3  0x4005cc8b in _PyBuiltin_Init () from /usr/lib/libpython2.1.so.0.0
> > ...
> 
> I'm afraid the traceback literally makes no sense:  PyTuple_SetItem never
> calls PyTuple_New, nor vice versa.  Ditto the other adjacent pairs.  The
> addresses may be correct, but the reported function names are wrong.

Hm, then I hope the other traceback that gave Matt a clue *was* 
correct. I've just run a plain gdb against Zope without trying a debug
build of either Python or the Zope modules. Should I try that? And
would this help? I have little experience in debugging Python on
this level, so some clues would be useful.

Regards,

Martijn