Mailing-List:	contact cygwin-developers-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-developers-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin-developers/>
List-Post:	<mailto:cygwin-developers AT cygwin DOT com>
List-Help:	<mailto:cygwin-developers-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-developers-owner AT cygwin DOT com
Delivered-To:	mailing list cygwin-developers AT cygwin DOT com
Message-ID:	<032501c23d0e$ba25a160$6132bc3e@BABEL>
From:	"Conrad Scott" <Conrad DOT Scott AT dsl DOT pipex DOT com>
To:	<cygwin-developers AT cygwin DOT com>
References:	<001e01c23cb5$403b4b10$6132bc3e AT BABEL> <20020805201505 DOT GA9710 AT redhat DOT com> <20020806053425 DOT GA14302 AT redhat DOT com>
Subject:	Re: cygthread + rxvt
Date:	Tue, 6 Aug 2002 07:01:37 +0100
MIME-Version:	1.0
X-Priority:	3
X-MSMail-Priority:	Normal
X-MimeOLE:	Produced By Microsoft MimeOLE V6.00.2600.0000

"Christopher Faylor" <cgf AT redhat DOT com> wrote:
> Yep.  That was an interesting race.  Like most races, it was
really
> obvious once I found it.

Sometimes I feel deflated after finding bugs: so interesting to
find but boring and trivial once found (and then there's testing).

> It seems to work ok now but I haven't tested it rigorously.  I
was lulled
> into a false sense of security before when I really *had* tested
rxvt.
> I just didn't try it enough times to notice that it failed 50%
of the
> time at least.

I'll add my 2c of testing in a moment.  And thanks for the mount_h
patch: from where I'd got in my vacant gazing at the code it looks
right.  I'm going to have to draw a bl**dy big picture of the
whole DLL initialization / fork / spawn system one day; either
that or continue to limp along and hope someone more knowledgable
will fix the problems I find (or create) :-)

Cheers for now,

// Conrad

- Raw text -