X-Recipient: archive-cygwin@delorie.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=J5o+F3ztnjx0cQ4zk1SNX0AKlAS3tj/krgby5KpAW0+tVVGVM4E/5
	CJGYu/MgOpr7gHsR10oS8EeONkr+5+DSENOKAjEfBpzjD02EDscQXg6WRpQkEZzz
	qn1In0HM0XNtetx2n7eGEIlE2G2rODBalt3K6G0AcNMnMhBdJgZKDc=
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=v43+nHizk27mBF9LR9sIyTSL1lA=; b=X+bQ6PEgNce92h6fbvNBE0hIaHKG
	U5Pr2HPI75n9Kpu6//rC+RDXfPeRHbUonBTh6YG4LE3vLgcCcTMgudiJ1EikNNJ3
	9S8Z6brAcQ3/jXCtgUAcSY5CgWhLEXpbR+wm1qKuAJG1EjsRGGzNotytIsSvarJp
	qm9W+GwGcvtQY5w=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-0.5 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@dyndns.com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information)
X-MHO-User: U2FsdGVkX1/O8bUc+18ByXiX8wn6ATO0
Date: Tue, 29 Oct 2013 16:59:35 -0400
From: Christopher Faylor <cgf-use-the-mailinglist-please@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Problem with multiprocessing module from Python
Message-ID: <20131029205935.GC392@ednor.casa.cgf.cx>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
References: <CAHhGz88t8H_xQ6h-a6-aQrMf+wTOVT6gMnx42tMpjs=3=qGVTQ@mail.gmail.com> <l4ei86$cos$2@ger.gmane.org> <l4p2uq$ps8$1@ger.gmane.org> <l4p6h3$801$1@ger.gmane.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <l4p6h3$801$1@ger.gmane.org>
User-Agent: Mutt/1.5.20 (2009-06-14)

On Tue, Oct 29, 2013 at 08:41:07PM +0000, Jean-Pierre Flori wrote:
>Le Tue, 29 Oct 2013 19:40:10 +0000, Jean-Pierre Flori a ??crit??:
>>> For your info, I was unable to reproduce such a behavior on Cygwin 32 v
>>> 1.7.25 installs running on 64 bits Windows 7 both on real hardware and
>>> VirtualBox 4.3...
>>> 
>> I went on with further testing and could reproduce the problem with the
>> Cygwin shipped Pythons on a 64 bit Windows 7 running under VirtualBox
>> 4.3 with Cygwin 64 and on a 32 bit Windows 7 running on real hardware
>> (intel Atom).
>> 
>> Best,
>> JP
>Same problem with Python 2.6.8 from Cygwin on the 32 bit Windows 7 running 
>on Intel Atom.

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.

--
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

