DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:date:message-id:subject:from:to
	:content-type; q=dns; s=default; b=vYT3JS37ad5JyUYi8/fEhepw+URC/
	pIk+9g6rw4YYqFBwieXYL4/S99c3CoynS3FUPG79vZjrvqYjx3BLOwTDBhDt1gOr
	Cm+pxEHMbR42m5Kt1LG6MhsJND7dpt/7uy+ARgwQtuvLBgKAnxX+xoCkiJkI2hk2
	G3R9e8MvDe+aDw=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
MIME-Version: 1.0
Date: Mon, 14 Apr 2014 06:27:50 -0400
Message-ID: <CAD3=EHuK57UKmsnozCUFcOv_AgfX0e6H7r6diRTgCNWf9pjjNQ@mail.gmail.com>
Subject: Re: find_fast_cwd warning persists after uninstalling (Windows 8.1 x64)
From: Mayank Patke <mayank DOT patke AT gmail DOT com>
To: cygwin AT cygwin DOT com
Content-Type: text/plain; charset=UTF-8

> 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).

I don't have much experience, but I know enough assembly to read it
and to do basic debugging. I haven't used WinDbg before, but I've used
other disassemblers as well as GDB. I'm willing to do this if someone
can let me know what I should be looking at/for.

> 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.

I'll do this if I (really, really) have to. As you say, this will take
some time, largely in rebooting, and that's just assuming it's Windows
Update and not another program.

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple