DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:cc:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=HUAGTTqDE7626fX1E6+l36bnjLkQaQbyklX3y4U+P7RDRsFl6LHlM
	kBdQMuo43wB21jgKOuFlQo55hX4biQeE2fLjv140vmpZ19LnJYQeXM5fHVQEd5GL
	Cu6aIfNGodYsmmJ61p8eggWXrJdYC+psOoMl4BniQGiRFeAf+NU8Uc=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Date: Thu, 22 Aug 2013 16:12:06 +0200
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Cc: Eric Blake <eblake@redhat.com>
Subject: Re: shell-init: error retrieving current directory
Message-ID: <20130822141206.GN2562@calimero.vinschen.de>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com, Eric Blake <eblake@redhat.com>
References: <521571A7.6010503@gmail.com> <521575A1.6020304@gmail.com> <52157710.7060509@gmail.com> <20130822111143.GL2562@calimero.vinschen.de> <5216089C.6080502@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;	protocol="application/pgp-signature"; boundary="O27Gs9jTTFWz3gAR"
Content-Disposition: inline
In-Reply-To: <5216089C.6080502@gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)

--O27Gs9jTTFWz3gAR
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Aug 22 21:48, nu774 wrote:
> Hi,
>=20
> It seems that getcwd() of bash continues the following approach
> until it reaches /.
>=20
> 1) readdir() on the parent directory.
> 2) for each dirent returned by readdir(), find the entry that
> matches the current dirctory (by comparing inode or something).
> 3) set parent dir as current, and continue from 1).
>=20
> When you call getcwd() not under / (that is, C:/cygwin64), say
> /c/foo/bar (here I assume C drive is mounted on /c), step 2) will
> fail when current is /c, since readdir() on / doesn't return c as a
> dirent.
>=20
> In short, getcwd() of bash doesn't work as expected in this
> situation, and if Cygwin's getcwd() implementation complies
> requirement by bash, HAVE_GETCWD should be enabled.
> As far as I can see, HAVE_GETCWD enabled bash.exe is working fine here.

Since our bash maintainer Eric is currently extremly busy, I took a stab
at it and created a new bash-4.1.11-2 64-bit package.  It picked up the
Cygwin getcwd and didn't have the reported problem in my quick test.

Please give it a try as soon as it hits your favorite mirror.


Thanks,
Corinna

--=20
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

--O27Gs9jTTFWz3gAR
Content-Type: application/pgp-signature

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

iQIcBAEBAgAGBQJSFhw2AAoJEPU2Bp2uRE+glIEQAImifd0fIzIIgOEBA1YPhwFP
zT79zOvYanCKB0BpAgNYCSBY0cMYywzHcVcH/gcu80uvwdzpV3Qd4tucSJkqwmko
CkvIK4y8oNNcgPJNUq83lFxKoc3cBQDp5AbjT3AaT8BeeptzL2oelaWodObh9XfY
PllprTmV9kjtU9qey96ChUFmjdpABxKtCVsuCV1sCxXMhbtAEgK4VFwAi/7XETR7
OILajeGJ3AqbM42M6gyvt6il2PpYtwQ92XoOr4e5VHww3FgfsITsGGk+clNn/jyy
V+C+RFzZVyy8G72nYMAiqT2GHblvsJnlGHY1FQjFolGmxBqzDkaxUWWxQHlFqPRz
CFAOowZgpLQCt1x2CKPXCkslzF39XwAzNNczuIR8hcCbarqVE4rz4Ds9q3szv0/q
oiBbzZ6GV8Vshi6H2gxW0RRJdSDghIbC5iCPUS8tAiQASezey/SITejlrzbF1RwQ
qcZBdZg+iBH5ROR6Tnhb9izgixVe2thWjfjQzNMeUo8yLkQXs5A8rZHLmZ1wjvKT
GUBQFYJbwMJN2ZXR/43NX0ny9WK1HjZ8oJpsyDQFj9qam21guM+ZqiYY3fV+kweA
Q+/PfAEvP2sZgHVPmhSVIcrofzmpHQKXDztiHyF/5XXBf4kD5epxJlgxfBtrJyCH
Yyu5W1t+GH1RrO7vT70a
=+4Uy
-----END PGP SIGNATURE-----

--O27Gs9jTTFWz3gAR--