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: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=
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:mime-version:date:message-id:subject:from:to
	:content-type; s=default; bh=M65ID1tB5zPffl85nanu2HXqhFo=; b=jg9
	JtbGxo0V1XYfLg1/N759DOSRVTWwIRTI8MC+i943Nmgre4/jlbEFWtLJ3TknZuCl
	BeQ6Hzwj/f53iGgD4rl4mAVO4HMcpcHCRFOslrL6bhTQGg2yfMHFAuDzwvEJojyr
	nompE7F/T6A2PJdT9uIUyXv5SHhWTP640JlzJ4cg=
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=-1.8 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2
X-HELO:	mail-oa0-f52.google.com
MIME-Version:	1.0
X-Received:	by 10.182.102.99 with SMTP id fn3mr1118275obb.57.1397471270205; Mon, 14 Apr 2014 03:27:50 -0700 (PDT)
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

> 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

- Raw text -