It does sound suspiciously like the freebsd python issue. What do you
get in the event log when python crashes ? Is it SIGSEGV(11)/SIGBUS(10)
or whatever ?
This tends not to get triggered with a zeo debug prompt, for whatever
reason.
To find out, you could:
- rebuild python with a very large stack - 1Mb *should* be enough
- rebuild python with debugging symbols, then run python/zope with gdb
and see what the stack trace says when it crashes.
- sprinkle the zope code with log statements until you narrow down where
the crash is happening. If it's the stack thing, it's probably in a call
to the re module.
_______________________________________________
Zope-Dev maillist - [EMAIL PROTECTED]
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope )
- [Zope-dev] Re: Zope 2.7 and object... Casey Duncan
- Re: [Zope-dev] Re: Zope 2.7 and ob... Florent Guillaume
- RE: [Zope-dev] Re: Zope 2.7 an... Sandor Palfy
- RE: [Zope-dev] Re: Zope 2.7 an... Dieter Maurer
- RE: [Zope-dev] Re: Zope 2.7 an... Tim Peters
- RE: [Zope-dev] Re: Zope 2.7 an... Dieter Maurer
- RE: [Zope-dev] Re: Zope 2.7 an... Dieter Maurer
- RE: [Zope-dev] Re: Zope 2.7 an... Tim Peters
- RE: [Zope-dev] Re: Zope 2.7 an... Sandor Palfy
- Re: [Zope-dev] Core Dump (Zope 2.7, Python 2.3.... Dieter Maurer
- Simon Michael