X-Recipient: archive-cygwin AT delorie DOT com DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:date:from:to:subject:message-id:reply-to :references:mime-version:content-type:in-reply-to; q=dns; s= default; b=lEqWsJk+4ek9bA6MvG0eAF530AJ193FXRL+EJMZMVK9jYNtJQAYDh rUcgwZLXQQq5V23jlB1sDmuvraVp+UQENhaMfqfPa7yFNN4uzI/aftIOGsCBbCWv KA4p+l7Vvxw+Jl3vQ3yGJeCO7pSMgEHyyz36Q9qWOVRl83IsM5nYcA= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:date:from:to:subject:message-id:reply-to :references:mime-version:content-type:in-reply-to; s=default; bh=NAoNdyPjQDKW/GcNvg5PgqC/N2s=; b=PAp1x6VzwrYudw6wy67ntGVhpJpQ Oq8OB49l7mhFi6s5LZsJSjC9HEYFA1BeXSd4A6OzDBaejw/4pnDYmAc+q9ImfkA0 ap7WpkuCYeqbmDBgOHPygqL18dlzmYkNU7VcLAlRU/pGFdpT4hhA5AO50GJlfgfi RRTz7kUz9XAETX0= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-0.6 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.2 X-HELO: mho-02-ewr.mailhop.org X-Mail-Handler: Dyn Standard SMTP by Dyn X-Report-Abuse-To: abuse AT dyndns DOT com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information) X-MHO-User: U2FsdGVkX19+cGAEVE86Fx1kwNdoH8VW Date: Thu, 31 Oct 2013 14:41:14 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: Problem with multiprocessing module from Python Message-ID: <20131031184114.GD6599@ednor.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <20131029205935 DOT GC392 AT ednor DOT casa DOT cgf DOT cx> <20131030093313 DOT GA28558 AT calimero DOT vinschen DOT de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) On Thu, Oct 31, 2013 at 06:27:39PM +0000, Jean-Pierre Flori wrote: >Le Wed, 30 Oct 2013 10:33:13 +0100, Corinna Vinschen a ??crit??: > >> On Oct 29 21:22, Jean-Pierre Flori wrote: >>> Le Tue, 29 Oct 2013 21:19:14 +0000, Jean-Pierre Flori a ??crit??: >>> >>> > Le Tue, 29 Oct 2013 16:59:35 -0400, Christopher Faylor a ??crit??: >>> >> If you want this fixed, the easiest way to get that to happen is to >>> >> post a simple test case which reproduces the problem. That is not >>> >> the code snippet that you sent. A real working example would be >>> >> required. >>> > Sorry about that. >>> > >>> > Here you go: >>> > """ >>> > from multiprocessing import Pool >>> > >>> > def f(x): return x >>> > >>> > p = pool(2) >>> > >>> > p.map(f, [1, 2]) >>> > """ >>> And I managed to introduce a typo. The third line should read Pool, so >>> it is: >>> """ >>> from multiprocessing import Pool >>> >>> def f(x): return x >>> >>> p = Pool(2) >>> >>> p.map(f, [1, 2]) >>> """ >> >> Works for me. I guess. At least, if I run the script, nothing happens: >> >> $ python x.py $ >> >> Same on 32 and 64 bit Cygwin. >> >> >> Corinna > >I think I got to the bottom of this. >It seems the new implem of sem_getvalue in cgwin1.dll is the cause, see: >http://cygwin.com/ml/cygwin-patches/2013-q3/msg00006.html >It may also explain the random reproducibility if sval stays uninitialized >or something like that (I did not check it is the case though). I doubt that was the problem. More likely it is something related to the changes in thread.cc that followed that change. cgf -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple