Mailing-List:	contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender:	cygwin-developers-owner AT sourceware DOT cygnus DOT com
Delivered-To:	mailing list cygwin-developers AT sourceware DOT cygnus DOT com
Date:	Thu, 29 Apr 1999 19:03:41 -0400
From:	Chris Faylor <cgf AT cygnus DOT com>
To:	Mumit Khan <khan AT xraylith DOT wisc DOT edu>
Cc:	cygwin-developers AT sourceware DOT cygnus DOT com
Subject:	Re: (patch) reg_key copy construction bug
Message-ID:	<19990429190341.A13641@cygnus.com>
References:	<19990429172018 DOT D13241 AT cygnus DOT com> <Pine DOT SUN DOT 3 DOT 93 DOT 990429174933 DOT 24161D-100000 AT modi DOT xraylith DOT wisc DOT edu>
Mime-Version:	1.0
X-Mailer:	Mutt 0.95.3i
In-Reply-To:	<Pine.SUN.3.93.990429174933.24161D-100000@modi.xraylith.wisc.edu>; from Mumit Khan on Thu, Apr 29, 1999 at 05:53:28PM -0500

On Thu, Apr 29, 1999 at 05:53:28PM -0500, Mumit Khan wrote:
>On Thu, 29 Apr 1999, Chris Faylor wrote:
>>I have to note that my cygwin1.dll is not crashing on startup, however.
>>That is not new code, is it?  Hasn't it been there for years/
>
>Interesting that it doesn't crash your machine.  It crashes an NT
>4.0SP3 machine, but not my W95 laptop and one other NT machine also
>running NT 4.0SP3.  Must be a difference in MS runtime versions
>installed by various MS packages.
>
>The change is actually quite recent.  B20.1 had the reference.  I
>believe it was part of the mount rewrite.

That would explain why there isn't a hue and cry on the cygwin mailing
list.

I know that DJ and I aren't seeing any crashes and it seems that other
people are running the snapshots.  Weird.  Maybe it has to do with
what's getting mounted?

Regardless, I'm relieved that you've found this.  I'm tentatively
scheduling a B21 release for mid-May so this could have been a real show
stopper.

-chris

- Raw text -