<br><br><div><span class="gmail_quote">On 12/17/06, <b class="gmail_sendername">Dieter Maurer</b> <<a href="mailto:dieter@handshake.de" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">dieter@handshake.de
</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Patrick Gerken wrote at 2006-12-13 16:13 +0100:<br>> ...<br>>Now we got the problem that zope randomly crashed.<br><br>There are many ways "crashed" can be interpreted.<br><br>If "crashed" means "died from a fatal signal" ("SIGSEGV", "SIGBUS",
<br>"SIGABORT", ...), then the analysis of the "core" file may provide<br>valuable insights.</blockquote><div><br>I am sometimes really bad in answering to helpful tipps :-(<br>The last look at it with strace showed that I should not try to debug this thing by using threads. I still dont know the exact signal he emits, but I know now that it is a problem independent of zope, the same access in pure python code now crashes too now and then. We will first try to upgrade to newer versions of python and then see again.
<br><br>Best regards,<br><br> Patrick Gerken<br><br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
--<br>Dieter<br></blockquote></div><br>