Included patch written by PieterB fixes an issue with Zope/ZWiki often
crashing with SIGBUS/SIGSEGV. I've tested it myself on 4-stable and it
seems to fix the problem.
Following URLs include more information:
Zope uses Python 2.2 now.
On Wed, Feb 05, 2003 at 01:36:28PM -0700, Alex Rodioukov wrote:
>On Wed, 2003-02-05 at 05:57, Alan Eldridge wrote:
>> Synopsis: python21 patch to increase the default thread stack size.
>> State-Changed-From-To: open->closed
>> State-Changed-By: alane
>> State-Changed-When: Wed Feb 5 04:57:28 PST 2003
>> Zope uses Python 2.2 now.
>Your statement is not true. Zope 2.x *requires* Python 2.1.x. From
>README.txt for 2.6.0 (current Zope stable version, also in ports):
> ZOPE 2.6 REQUIRES PYTHON 2.1.X!
> Note: Using Python 2.2 is not recommended and not supported.
I'll admit it, I was lax when I patched it (from a submitted patch).
If this patch is officially recommended by Zope, I will apply it.
In either event, I will change the Makefile for the Zope port so
that it once again requires Python 2.1.x. I'm sorry about that
If the patch is not recommended by Zope itself, then I'll have to
think about how to handle this. Python is a large and complex program,
and a patch that changes functionality is not to be taken lightly.
AlanE (Alan Eldridge)
Unix/C(++) IT Pro for 20 yrs, likes fixing weird distributed systems bugs.
KDE, KDE-FreeBSD Teams (http://www.kde.org, http://freebsd.kde.org/)
Re-open for investigation. Closing was my error.
On Wed, 2003-02-05 at 14:22, AlanE wrote:
> I'll admit it, I was lax when I patched it (from a submitted patch).
> If this patch is officially recommended by Zope, I will apply it.
> In either event, I will change the Makefile for the Zope port so
> that it once again requires Python 2.1.x. I'm sorry about that
You might want to check the links I've supplied with the PR. My
understating is that the problem the patch fixes is with default small
per-thread stack size allocated by Python on FreeBSD, which under some
conditions causes Python process to SIGSEGV. I've encountered it with
Zope under heavy loads. Another example is ZWiki. Many people were
bitten by it, see:
> If the patch is not recommended by Zope itself, then I'll have to
> think about how to handle this. Python is a large and complex program,
> and a patch that changes functionality is not to be taken lightly.
Certainly so. I would encourage you to do the research yourself. Let me
know if you'll need any help.