Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Subject: Re: Mysterious gdb behavior.
From: Robert Collins <rbcollins@cygwin.com>
To: derbyshire@globalserve.net
Cc: cygwin@cygwin.com
In-Reply-To: <3D4B18D6.3227.70F36118@localhost>
References: <3D49FDDB.3878.6C9D6B31@localhost> 
	<3D4B18D6.3227.70F36118@localhost>
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature";
	boundary="=-qOkC1TkjTkS2a2jZ0R+Y"
Date: 03 Aug 2002 17:27:10 +1000
Message-Id: <1028359630.9565.99.camel@lifelesswks>
Mime-Version: 1.0

--=-qOkC1TkjTkS2a2jZ0R+Y
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

On Sat, 2002-08-03 at 13:42, Paul Derbyshire wrote:
> It just gets worse doesn't it? The last time I made an ill-advised=20
> manual registry tweak it took days to restore the system to a known=20
> good state. I'm not risking that again. Anyway, It Should Not Be=20
> Necessary to Fuck With The Registry To Make Cygwin Work As Designed.

Cygwin is not perfect. I see in another email that you have tested and
found that the directory name with a space in it is the issue.

You have now identified the exact situation that results in your error.

You have also recieved free advice on several methods that may alter
your situation to one that will work, it's up to you to choose the
method that you prefer.=20

This thread is now off-topic. A summary message from you on how you
correct it (once you choose a method) would be good for the list
archives.

Rob

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

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iEYEABECAAYFAj1Lhc4ACgkQI5+kQ8LJcoLxygCcCLZN37LYBjCAI+MLh8XbLzaM
nZgAn0ssD4z/avnCtYFCvheGwJOhKpT1
=0Xoa
-----END PGP SIGNATURE-----

--=-qOkC1TkjTkS2a2jZ0R+Y--