Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Subject: RE: Cygwin causes 0x00000024 Stop Error (BLUE SCREEN)
From: Robert Collins <rbcollins@cygwin.com>
To: Randall R Schulz <rrschulz@cris.com>
Cc: cygwin@cygwin.com
In-Reply-To: <5.1.0.14.2.20021124134357.02ad0608@pop3.cris.com>
References: <5.1.0.14.2.20021124131806.03241008@pop3.cris.com>
	<00bf01c293d6$c62800b0$78d96f83@pomello>
	<5.1.0.14.2.20021124131806.03241008@pop3.cris.com> 
	<5.1.0.14.2.20021124134357.02ad0608@pop3.cris.com>
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature";
	boundary="=-dNXHpVPMEiQl4JuIGOUD"
Date: 25 Nov 2002 10:48:34 +1100
Message-Id: <1038181718.23988.127.camel@lifelesswks>
Mime-Version: 1.0

--=-dNXHpVPMEiQl4JuIGOUD
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

On Mon, 2002-11-25 at 08:52, Randall R Schulz wrote:

> If KB 195857 really is the culprit here, then I suppose you could well ma=
ke=20
> the case that opening a lot of system handles and then just abandoning th=
em=20
> is not good programming practice and really should be resolved on its own=
=20
> merits.

Yep. Although, I'm not convinced, just open minded, and willing within
reason to change setup to deal with OS bugs, as the OS is not free.

> I take it hardware configuration (available RAM and / or paging space) is=
=20
> one a parameter in the likelihood of triggering this problem.

I have *no* idea.=20

Cheers,
Rob
--=20
---
GPG key available at: http://users.bigpond.net.au/robertc/keys.txt.
---

--=-dNXHpVPMEiQl4JuIGOUD
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQA94WVRI5+kQ8LJcoIRApiPAJ0We/PwtWodX0GXrZGMfQ/z3KOUFQCgg4I7
zCAUdR8RtgaGlRLo9x+zFBA=
=8RHj
-----END PGP SIGNATURE-----

--=-dNXHpVPMEiQl4JuIGOUD--