Hi Zopers! Thanks all for your time, especially to Matthew and Leonardo. My patched Python/Zope systems run well now in multi-threads mode. I tested with very hard Python Scripts too and my report is at all positive. My relief is great, like many others zopers, I think ; ) Thanks again and Happy Easter! Stefano ---------------------------------------------------------- Stefano Noferi n o z e S.r.l. Soluzioni Open-Source Via Caduti del Lavoro, 32 56122 Pisa (PI) - Italy Tel: +39 (0)50 533320 Fax: +39 (0)50 526604 Email: stefano@noze.it Web: http://www.noze.it ----------------------------------------------------------
Stefano Noferi wrote:
Hi Zopers!
Thanks all for your time, especially to Matthew and Leonardo. My patched Python/Zope systems run well now in multi-threads mode. I tested with very hard Python Scripts too and my report is at all positive.
My relief is great, like many others zopers, I think ; )
Thanks again and Happy Easter!
Stefano
FYI, Pythonlabs thinks there is more than one bug involved. The relevant report at sourceforge is: http://sourceforge.net/tracker/?func=detail&atid=105470&aid=535905&group_id=... -- Matt Kromer Zope Corporation http://www.zope.com/
On Thu, 2002-03-28 at 15:33, Matthew T. Kromer wrote:
[...] FYI, Pythonlabs thinks there is more than one bug involved. The relevant report at sourceforge is:
http://sourceforge.net/tracker/?func=detail&atid=105470&aid=535905&group_id=...
That report marks the bug as closed and one of the comments by Guido states that the ceval.c.diff and trashcan_gc.diff patches are enough to fix the problem for good (if I read it correctly). but the trash-2.1.2.diff seems to contain some important reorderings that are related to the TRASHCAN and the GC, so now I'm not sure. I also tried taking a diff between the 2.1.2 release and the python 2.1 maintenance branch on CVS, but my cvs skills still aren't that good :-) Which is (or where can I find) the currently official patchset to apply against Python-2.1.2 source? -- Ideas don't stay in some minds very long because they don't like solitary confinement.
On Mon, 2002-04-01 at 19:57, Leonardo Rochael Almeida wrote:
On Thu, 2002-03-28 at 15:33, Matthew T. Kromer wrote:
[...] The relevant report at sourceforge is:
http://sourceforge.net/tracker/?func=detail&atid=105470&aid=535905&group_id=... [...] Which is (or where can I find) the currently official patchset to apply against Python-2.1.2 source?
When you want something done right you just go and do it yourself, right? Attached is a patch for the Python source that was taken from a diff of the 2.1 maintenance branch against the original 2.1.2 release, cleaned up so that it only contains modifications that are relevant to the crash problems. To make it your self you should get a Python cvs sandbox (instructions here http://sourceforge.net/cvs/?group_id=5470 the CVS module is python) get into the python/dist/src directory and run this command: cvs -z3 -d:pserver:anonymous@cvs.python.sourceforge.net:/cvsroot/python diff -u -kk -r r212 -r release21-maint Modules/gcmodule.c Objects Python
../../../segfault-fix.diff
(If my MUA wrapped it, it's all in one line, obviously) I just put this patch up in production environment and it's been up for more than 1h30m now, which for me is enough indication that it's in fact the final solution to the problem. Cheers. -- Ideas don't stay in some minds very long because they don't like solitary confinement.
participants (3)
-
Leonardo Rochael Almeida -
Matthew T. Kromer -
Stefano Noferi