X-Recipient:	archive-cygwin AT delorie DOT com
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:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=wnVe4RZ+h/sGzb8bAbTElkL2jNW2Lss2ruxicBtY4EJoaCrCheKwV
	32GwG2dVU8EN+aMwg9HyAJ6aKegqVvbZJJ9wAV0vakROwb31rJqjW9Luou4fY+SZ
	Ek46f8USUlWlt4aT2R9xoFMbXASa7Cuydp05WjxQO6Cp4l8jsE0jOg=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; s=default;
	bh=+3g5fTS1ZYoqxg7A+aEBGd1f/tE=; b=Relh+RzsjDv6Z4qOeLGV3X4P/z9u
	TecStBzJMDOKYtSxIydMlbkjSmvxrA1N4GGLFJTF3U4UtAdtZCt4kphhavpwapL/
	p4pM0c1AcXhLTsgVML2fyoFkIGsFqs8XNLgAiXZ4eDYJef0RWcX6Frg35BBYni72
	K7+86zjE8v+8sws=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Authentication-Results:	sourceware.org; auth=none
X-Virus-Found:	No
X-Spam-SWARE-Status:	No, score=-5.9 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.3.2
X-HELO:	calimero.vinschen.de
Date:	Mon, 14 Apr 2014 12:11:52 +0200
From:	Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: find_fast_cwd warning persists after uninstalling (Windows 8.1 x64)
Message-ID:	<20140414101152.GA24891@calimero.vinschen.de>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<CAD3=EHs45s++LOJRz7mZRzco_HQ5HsPHZ+o_k0zrK2NoNNhy+A AT mail DOT gmail DOT com>
MIME-Version:	1.0
In-Reply-To:	<CAD3=EHs45s++LOJRz7mZRzco_HQ5HsPHZ+o_k0zrK2NoNNhy+A@mail.gmail.com>
User-Agent:	Mutt/1.5.21 (2010-09-15)

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

On Apr 14 05:23, Mayank Patke wrote:
> > I already wrote two mails on this to this list.  I'm running Windows
> > 8.1 32 and 64 bit, but on my machines, the find_fast_cwd warning is
> > not printed, so the find_fast_cwd mechanism works as expected.
>=20
> Right, I saw those in the search results, although I didn't find any
> instances of someone uninstalling and having the same problem. Though,
> as you say, it's likely MSYS which is responsible on my system.
>=20
> > To get rid of this message, either I have to know how to reproduce it,
> > or somebody with this problem would have to debug a teeny little bit
> > of assembler code inside the Windows ntdll.dll file.
>=20
> I'm willing to debug, but I'd need someone to step me through this.
>=20
> > To be able to reproduce it, I would need somebody who can reproduce the
> > problem and being prepared to experiment a bit.  It *seems* the problem
> > is introduced by some Windows update package which is not installed by
> > Windows Update by default.  If we can find out which package this is,
> > I could debug this and get rid of the message.
>=20
> Still willing to help.
>=20
> I'm not sure what level of expertise you're looking for, but I'll do
> whatever I can to help get this resolved.

Debugging is tricky unless you have experience with how to debug
assembler code and know a bit about x86/AMD64 assembler and how to use
WinDbg.  A high level of capacity for suffering might help, too ;)  It's
not a lot of code you would have to look at, basically just the first
100 or so bytes within two functions in ntdll.dll are affected.  If
you're basically comfortable with that, we could arrange a debugging
session via IRC (Freenode).

The other choice is not to debug, but trying to find out what Windows
Update or what software package introduced the problem.  This is not
overly tricky, but could take lots of hours and needs lots of patience.
You would have to deinstall Windows Updates, reboot, try again,
re-install, remove other Windows Updates, try again... up to the point
where the find_fast_cwd message disappears.  Also, software packages
like virus scanners, firewalls, and especially Microsoft software could
have introduced the problem and deinstalling and later reinstalling
might do the trick.,.  and then I would have to install the culprit and
debug the problem myself.

Sigh, I would be glad if I could reproduce this right now.  That would
be a lot easier for everybody.


Corinna

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

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

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBAgAGBQJTS7RoAAoJEPU2Bp2uRE+g9EEP/RlOHsiaRidoC2FLkX8pTDrZ
PLRsJwopGQ7QrR6OXCu2MLScfzOqeMARoqWRdJNRGewhV5tuLNJYhgalHI9qxMz4
WEu1w6BYMzZHJ0JLMqc7LfHWw25wda+MfxgEfH4+KC4PS5oGEQ+r2H0PwmYjeOEw
4br8PSyEQvhaT2aytcSd1oNxLz32HNOD4a6AFB853o0fw5D5swXOG2aKIqwZZvDB
D8V2B5K990oUTgyrsQh75SCvWaar4epgy+kM3kgHdr5yJn37Y/BlJVfMDOrqkQkI
O4M/ZvUgp9XNN1QCazX4Oxr+7YONnwkVZuJ0uKLEX2ToSxHos2Wz/NExW+zHS9YZ
aHPUpojtDvvsJMyKATtv7Yt/pmceZ32SiLCT1WOYwYbDNbT9L3+n56p0VwsDjGMx
vm88DsB2J0qthd22J52xxHn886u5PjDeJIdwJFhPIzF1hqCdS4LhOYrvFAN4KL2M
E5r6c97GgmQPxKexkJbWZta75mzqi9nUOavkZiKkhLY6DLsmzUnH0zCo5MeqMRGn
VYyAr5Iph+Bbsu1RXL82BZEW9QUmTlnNPKBMCHow1G2wDjkEcWCAx9sp051vQi4v
AANXkojdR12wSAfS0/M572W6R4l8V4L7MYflzpOO1eAmWrdgDwC2fwszq+3NiBSr
l6oRkJdCBeY0OwlPYU2p
=Tw1t
-----END PGP SIGNATURE-----

--ZGiS0Q5IWpPtfppv--

- Raw text -