Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
From: "Marcus Lindblom" <d98macke AT dtek DOT chalmers DOT se>
To: "'Elfyn McBratney'" <elfyn-cygwin AT exposure DOT org DOT uk>,
   "'cygwin'" <cygwin AT cygwin DOT com>
Subject: RE: ViewCVS problems
Date: Wed, 29 Jan 2003 18:35:44 +0100
Message-ID: <000001c2c7bc$da274160$91f70bc1@fizzgig>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
Importance: Normal
In-Reply-To: <02e201c2c7b7$d2f2df30$a2e786d9@webdev>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106

> > Since it's thrown on os.fork(), I suspect cygwin is the culprit, but
> > that's just my gut feeling.
> 
> There have been some changes in the fork-semantics (?) AFAIKS 
> in the latest
> snapshots. Also what heppens if you roll back to cygwin-1.3.18-1?

I didn't know about the possibility of rollback.

Rolling back cygwin didn't help, but rolling back Python did!
(From 2.2.2-4 to 2.2.2-1)

/Marcus


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/