Hi, I decided to upgrade my Python 2.1.1 to Python 2.1.2 (in order to gently move to 2.5 later). My Zope instances were working quite fine....but...randomly I got a core dump (!) and the following message in logs : assertion "STACK_LEVEL() <= f->f_stacksize" failed: file "Python/ceval.c", line 687 Bug seems to appear when playing with ZCatalog (CMF sites could'nt even render a page) and Python scripts ? After some hours of researches, I have a (dirty, really) fix : I had to modify Python sources and hack line 687 in ceval.c : I removed it... Then recompile and it seems to work. I know this is dirty, and my Zope my crash later. PLEASE CHECK and HELP ! This looks like a major serious bug to me. Cheers, Olivier.
Olivier, Have you been reading anything about the random Zope crashes on the list for the last six months? Have you searched the maillist archives for the text of your crash? - C ----- Original Message ----- From: "Olivier Deckmyn" <odeckmyn.list@teaser.fr> To: <cmf-zope@zope.org>; <zope-dev@zope.org> Sent: Sunday, January 27, 2002 11:45 AM Subject: [Zope-dev] [BUG] Python 2.1.2 & Zope 2.4.1
Hi,
I decided to upgrade my Python 2.1.1 to Python 2.1.2 (in order to gently move to 2.5 later).
My Zope instances were working quite fine....but...randomly I got a core dump (!) and the following message in logs :
assertion "STACK_LEVEL() <= f->f_stacksize" failed: file "Python/ceval.c", line 687
Bug seems to appear when playing with ZCatalog (CMF sites could'nt even render a page) and Python scripts ?
After some hours of researches, I have a (dirty, really) fix :
I had to modify Python sources and hack line 687 in ceval.c : I removed it... Then recompile and it seems to work. I know this is dirty, and my Zope my crash later.
PLEASE CHECK and HELP !
This looks like a major serious bug to me.
Cheers,
Olivier.
_______________________________________________ Zope-Dev maillist - Zope-Dev@zope.org http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
What you just 'fixed' is an assertion against a memory corruption bug in all Zope versions between 2.4.0 and 2.4.3, inclusive. Zope version 2.4.4 (which hasn't been released, Hey ZC! wake up! stabilizing 2.4 is more important than releasing 2.5 in my book! Now that you've done the latter can you care to do the former, please? :-), should fix your problem, as would migrate to Zope 2.5. Legend has it that the current 2.4 branch is exactly what 2.4.4 will be. Check the archives for this mailing list (link below) for instructions on how to take the current 2.4 branch from CVS. BTW, Chris, what Olivier saw couldn't automatically lead him to correlate with the other Zope crashes, since the other reports don't mention the 'assertion' error message he saw, which he concluded was the cause of his problems. I'm really disappointed with ZC for putting out a new release of Zope instead of a fixed version of the release most everyone is currently using. Regards, Leo On Sun, 2002-01-27 at 14:45, Olivier Deckmyn wrote:
Hi,
I decided to upgrade my Python 2.1.1 to Python 2.1.2 (in order to gently move to 2.5 later).
My Zope instances were working quite fine....but...randomly I got a core dump (!) and the following message in logs :
assertion "STACK_LEVEL() <= f->f_stacksize" failed: file "Python/ceval.c", line 687
Bug seems to appear when playing with ZCatalog (CMF sites could'nt even render a page) and Python scripts ?
After some hours of researches, I have a (dirty, really) fix :
I had to modify Python sources and hack line 687 in ceval.c : I removed it... Then recompile and it seems to work. I know this is dirty, and my Zope my crash later.
PLEASE CHECK and HELP !
This looks like a major serious bug to me.
Cheers,
Olivier.
_______________________________________________ Zope-Dev maillist - Zope-Dev@zope.org http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
BTW, Chris, what Olivier saw couldn't automatically lead him to correlate with the other Zope crashes, since the other reports don't mention the 'assertion' error message he saw, which he concluded was the cause of his problems.
http://zope.nipltd.com/public/lists/zope-archive.nsf/47ba74c812dbc5dd8025687 f0024bb5f/2cd3e5f0b7deba7880256b48007583a8?OpenDocument&Highlight=0,ceval.c http://zope.nipltd.com/public/lists/zope-archive.nsf/47ba74c812dbc5dd8025687 f0024bb5f/16dea7ad623f53e080256b4c00742ba5?OpenDocument&Highlight=0,ceval.c
I'm really disappointed with ZC for putting out a new release of Zope instead of a fixed version of the release most everyone is currently using.
I'm really disappointed that you're disappointed. Folks, please get off of our backs for a second. We know it's important to release 2.4.4, it will be out soon. *Please* don't send us "wake up!" messages. We're fully awake and as soon as humanly possible, 2.4.4 will be out. Until then, hang tight. Folks here are working very hard. I think that Zope 2.5 was supposed to be released at the same time as Zope 2.4.4, but folks saw that the downloadable version of 2.5 up on Zope.org and assumed it was OK to put a news report out about it. It wasn't actually "released" as much as "escaped". ;-) - C
Leonardo Rochael Almeida wrote:
I'm really disappointed with ZC for putting out a new release of Zope instead of a fixed version of the release most everyone is currently using.
2.4.4 is ready, but there's a problem with the Windows build. I suppose we could just put the others up there w/out the Windows build, but then we'd wind up with 20 emails to reply to and explain over and over. All in all, only a few days separate the two releases, and obviously CVS people have been able to get at changes all along. Thus, I don't think this is an extreme case. --Paul
On Mon, Jan 28, 2002 at 10:32:11AM -0500, Paul Everitt wrote:
All in all, only a few days separate the two releases, and obviously CVS people have been able to get at changes all along. Thus, I don't think this is an extreme case.
Also note that downloading a source release from CVS is very very very easy. Just use the following link: http://cvs.zope.org/Zope/Zope.tar.gz?tarball=1&only_with_tag=Zope-2_4-branch This will get you a tarball with a CVS export of the current 2.4.x branch, which will contain *exactly* the same contents as the Ssource release we'll make as soon as the windows problem is resolved. -- Martijn Pieters | Software Engineer mailto:mj@zope.com | Zope Corporation http://www.zope.com/ | Creators of Zope http://www.zope.org/ ---------------------------------------------
participants (5)
-
Chris McDonough -
Leonardo Rochael Almeida -
Martijn Pieters -
Olivier Deckmyn -
Paul Everitt