Dieter Maurer wrote:
Samuel Bieri wrote at 2005-5-7 23:45 +0200:I managed to compile GNU debug 6.1.1 on the hp-ux box. When I run zope inside gdb I get the following:
When I click on a tal-object ("Page Template") to edit it, then zope stops responding. No error is logged, nothing. I even cannot stop zope anymore with "zopectl stop" or control-c if started with runzope. It seems that zope silently crashes... However, I can create a tal-object, it only happens when I try to edit.
Try to run Zope inside a debugger.
2005-05-08T22:29:59 INFO(0) Zope Ready to handle requests
[New thread 2 (system thread 9556080)]
[New thread 3 (system thread 9556082)]
[New thread 4 (system thread 9556083)]
[New thread 5 (system thread 9556084)]
---> here I klick on a tal-obect in zope. Zope freezes. Then I kill zope.
Program received signal SIGQUIT, Quit. 0x77d2ca58 in __lwp_sema_wait () from /usr/lib/librt.2
(gdb) bt #0 0x77d2ca58 in __lwp_sema_wait () from /usr/lib/librt.2 #1 0x77d2ba78 in sem_wait () from /usr/lib/librt.2 #2 0x77d2ba10 in sem_wait () from /usr/lib/librt.2 #3 0x77d2ba10 in sem_wait () from /usr/lib/librt.2 Previous frame identical to this frame (corrupt stack?) (gdb)
Can any experienced zope programmer help me further? What does this mean?
Thank you very much,
Zope maillist - Zope@zope.org
** No cross posts or HTML encoding! **
(Related lists - http://mail.zope.org/mailman/listinfo/zope-announce