Re: Python 2.1.2 does not fix the signal 11 crashing problem !!!!!!!!!!!
Harald Koschinski wrote Hallo,
after switching to python 2.1.2 compiled with GC (intranet:/usr/local/src/Python-2.1.2 # ./configure --without-pymalloc) the crashes are back again :-(((((((((((((((((((((((
Which version of Zope? Does it have the RestrictedCompiler fix? As far as I am aware, Zope 2.4 includes it's own version of the Compiler code, and the current release of 2.4 still has the stacksize bug. Anthony -- Anthony Baxter <anthony@interlink.com.au> It's never too late to have a happy childhood.
Anthony Baxter wrote:
Harald Koschinski wrote
Hallo,
after switching to python 2.1.2 compiled with GC (intranet:/usr/local/src/Python-2.1.2 # ./configure --without-pymalloc) the crashes are back again :-(((((((((((((((((((((((
Which version of Zope?
2.4.3
Does it have the RestrictedCompiler fix?
Good question - next question please :-((( I am again a little bit confused - I thought that the problem is only in the GC module of Python because zope is running without any crashes when I disable GC.
As far as I am aware, Zope 2.4 includes it's own version of the Compiler code, and the current release of 2.4 still has the stacksize bug.
Anthony
Matthew: Can you give the final answer ???
Yes, there is still a "compiler module" bug in Zope 2.4.3 that will cause crashing under any Python version. Please wait for Zope 2.4.4 (ETA unknown) or upgrade to Zope 2.5.0b4 (which already has the fix). - C ----- Original Message ----- From: Harald Koschinski To: Anthony Baxter Cc: Matthew T. Kromer ; Leonardo Rochael Almeida ; Ralph Arenz ; zope-dev Sent: Monday, January 21, 2002 4:23 AM Subject: [Zope-dev] Re: Python 2.1.2 does not fix the signal 11 crashing problem !!!!!!!!!!! Anthony Baxter wrote: Harald Koschinski wrote Hallo,after switching to python 2.1.2 compiled with GC (intranet:/usr/local/src/Python-2.1.2 # ./configure --without-pymalloc)the crashes are back again :-((((((((((((((((((((((( Which version of Zope? 2.4.3 Does it have the RestrictedCompiler fix? Good question - next question please :-((( I am again a little bit confused - I thought that the problem is only in the GC module of Python because zope is running without any crashes when I disable GC. As far as I am aware, Zope 2.4 includes it's own version of theCompiler code, and the current release of 2.4 still has the stacksizebug.Anthony Matthew: Can you give the final answer ???
Harald Koschinski wrote:
Anthony Baxter wrote:
Harald Koschinski wrote
Hallo,
after switching to python 2.1.2 compiled with GC (intranet:/usr/local/src/Python-2.1.2 # ./configure --without-pymalloc) the crashes are back again :-(((((((((((((((((((((((
Which version of Zope?
2.4.3
Does it have the RestrictedCompiler fix?
Good question - next question please :-(((
I am again a little bit confused - I thought that the problem is only in the GC module of Python because zope is running without any crashes when I disable GC.
As far as I am aware, Zope 2.4 includes it's own version of the Compiler code, and the current release of 2.4 still has the stacksize bug.
Anthony
Matthew: Can you give the final answer ???
2.4.4 (which should be mostly the equivalent of the Zope-2_4-branch in our CVS) hasn't been extensively tested. There are a LOT of things that I'm aware of that _can_ cause crashes, ie in MySQL when the database object switches threads, it can get unhappy (I think something in MySQL may have thread-local state). Unfortunately, I can't speculate on exactly WHICH problem is causing the seg faults, because they don't occur in-house (except for the one compiler bug which we were able to reproduce.) I am notionally toying with the idea of spending some evening hours attempting to come up with some kind of Linux-enabled crash capturing package, but this is not necessarily going to be trivial, and I dont know exactly how I want it to work. (Ie the proper way is to be able to validate all pointers etc, from the stack frame trace on a sig 11 signal handler etc.. but that may require some assembly glue).
At Mon, 21 Jan 2002 10:17:23 -0500, Matthew T. Kromer wrote:
2.4.4 (which should be mostly the equivalent of the Zope-2_4-branch in our CVS) hasn't been extensively tested. There are a LOT of things that I'm aware of that _can_ cause crashes, ie in MySQL when the database object switches threads, it can get unhappy (I think something in MySQL may have thread-local state).
I wanted to follow-up on this issue and share a little of my updates since I need a version of Zope as close as possible 2.4.3 but with the compiler fixes included to reduce the number of zope restarts. There are some particular reasons why we cannot wait until the release of 2.4.4. Anyway ... so based on my understanding that the Zope-2_4-branch contains the restricted compiler fixes and used in conjunction with Python 2.1.2, I should be able to have a reasonably stable version of Zope. So, I did the following steps (all on the linux platform) .... 0) Installed Python 2.1.2 with only the additional threading option. 1) Checked out the Zope-2_4-branch using cvs. 2) Applied the ExtensionClass.h patch. 3) Removed the following directories since these are in the way for my 2.4.3-like release installation: rm -R Zope-2.4.4a-src/lib/python/TAL rm -R Zope-2.4.4a-src/lib/python/Products/PageTemplates rm -R Zope-2.4.4a-src/lib/python/Products/STXDocument rm -R Zope-2.4.4a-src/lib/python/Products/Sessions rm -R Zope-2.4.4a-src/lib/python/Products/Transience rm -R Zope-2.4.4a-src/lib/python/Products/TemporaryFolder rm -R Zope-2.4.4a-src/lib/python/ZTUtils 4) I then performed a diff against my previous Zope-2.4.3 installation to see just what has changed. The only noticeable differences that are not included in the doc/CHANGES.txt are some modifications made to the file lib/python/ZODB/Mount.py. Otherwise, the changes pretty much match the CHANGES.txt doc (as best as I can tell). 5) I ran all of the unittests and they checked out fine. 6) I then installed this new version of zope (and zeo) and backed up our current zodb database. 7) Finally, I started up zope/zeo and tested our applications in the development environment and everything seems to be working fine. Unfortunately, the number of zope restarts is really unknown until this version is placed in our production environment. I have placed the diff against my old Zope-2.4.3 baseline and the ExtensionClass.h patch at the following URLS: http://www.zope.org/Members/natsukashi/Patches/Zope-2.4.4a-src-diff.txt http://www.zope.org/Members/natsukashi/Patches/Zope-2.4.4a-src-p1.txt I would appreciate any other persons with similiar needs to repeat steps similar as above and let me know if the face any troubles, etc. regards, - j
On Wednesday, January 23, 2002, at 03:30 AM, Joseph Wayne Norton wrote:
2) Applied the ExtensionClass.h patch.
For what its worth, we have decided NOT to use the ExtensionClass.h patch for 2.5 or 2.4.4. We haven't found that it made anything more stable, and it does a trick with a macro that could potentially break other people's extension class modules.
participants (5)
-
Anthony Baxter -
Chris McDonough -
Harald Koschinski -
Joseph Wayne Norton -
Matthew T. Kromer