Re: [Zope-dev] What does error code 136 mean?

2002-09-12 Thread Peter Keller
Hi, I have tried Leonardo's very helpful suggestion to get a Python traceback: Try to run zope under a debugger. Follow instructions here: http://www.zope.org/Members/4am/debugspinningzope but type continue (w/out quotes) as soon as you get the gdb prompt to get zope to run normally.

Re: [Zope-dev] What does error code 136 mean?

2002-09-04 Thread Peter Keller
Leonardo, Many thanks for the hints. I will investigate, but I probably won't have time until next week. Of course, this all depends on how well gdb (or your preferred debugger, should you chose to adapt the instructions) works correctly with threads on True64. In my experience, the Tru64

Re: [Zope-dev] What does error code 136 mean?

2002-09-03 Thread Leonardo Rochael Almeida
On Tue, 2002-09-03 at 06:25, Peter Keller wrote: Hi, I am having trouble with the current version of ZWiki. ZWiki's author is puzzled, and suggested that I try one of the Zope lists. I set up a ZCatalog on a ZWiki folder as described at http://zwiki.org/HowToInstallAZwikiCatalog The

Re: [Zope-dev] What does error code 136 mean?

2002-09-03 Thread Dieter Maurer
Peter Keller writes: ... with stupid log enabled I get this message: 2002-09-02T09:57:30 ERROR(200) zdaemon zdaemon: Mon Sep 2 10:57:30 2002: Aiieee! 322190 exited with error code: 136 This is signal 8 (136 - 128). On my Linux, this is SIGFPE (Floating Point Exception). Check