[Zope] Re: zope2.6.4/python2.2 doesn't restart after crash, with python2.1 it does

Jonas Meurer jonas at freesources.org
Tue Nov 9 11:12:43 EST 2004


On 09/11/2004 Andrew Langmead wrote:
> In python 2.2 and 2.3, signals are blocked on all threads except the  
> main thread. This causes problems with synchronous signals like SIGSEGV  
> which are always sent to the faulting thread.
> 
> See  
> <https://sourceforge.net/tracker/index.php? 
> func=detail&aid=756924&group_id=5470&atid=105470> or  
> <https://sourceforge.net/tracker/index.php? 
> func=detail&aid=468347&group_id=5470&atid=305470> for more details.

interesting! so this is not a zope bug.

> Since Python 2.4 hasn't been well tested for Zope yet, the suggestions  
> that I can think of are:
> 
> 1. Backport the threading/signal changes to 2.3.
> 2. Continue using 2.1.
> 3. Spearhead a movement to test Zope with Python 2.4. (someone has to  
> be the first over the hill.)
> 4. Find what is causing the seg fault, and avoid the issue entirely.

choices 1. and 3. take to much time, and choice 2. isn't a choice, as we
use python2.2 quite now.

4. is what i really try to do, but i didn't find any approaches yet.

bye
 jonas


More information about the Zope mailing list