Re: find_fast_cwd warning persists after uninstalling (Windows 8.1 x64)

Re: find_fast_cwd warning persists after uninstalling (Windows 8.1 x64)

[Mayank Patke]

> Cool!  For a start, what you could do is to install WinDbg(*) and the
> Windows 8.1 symbol package(**).  You also need at least a base
> installation of Cygwin, plus the cygwin-debuginfo and gdb packages.
> That should be enough to get us going.

I already have WinDbg and I just installed the symbol package and
reinstalled Cygwin, so I should be good to go.

~ Mayank Patke

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

Re: find_fast_cwd warning persists after uninstalling (Windows 8.1 x64)

[Corinna Vinschen]

[-- Attachment #1: Type: text/plain, Size: 708 bytes --]

On Apr 14 07:24, Mayank Patke wrote:
> > Cool!  For a start, what you could do is to install WinDbg(*) and the
> > Windows 8.1 symbol package(**).  You also need at least a base
> > installation of Cygwin, plus the cygwin-debuginfo and gdb packages.
> > That should be enough to get us going.
> 
> I already have WinDbg and I just installed the symbol package and
> reinstalled Cygwin, so I should be good to go.

FTR, in private mail it turned out to be a problem with a stray,
older Cywgin DLL which was earlier in $PATH sometimes.


Corinna

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

[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]

Re: find_fast_cwd warning persists after uninstalling (Windows 8.1 x64)

[Corinna Vinschen]

[-- Attachment #1: Type: text/plain, Size: 1486 bytes --]

On Apr 14 06:27, Mayank Patke wrote:
> > 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.

Cool!  For a start, what you could do is to install WinDbg(*) and the
Windows 8.1 symbol package(**).  You also need at least a base
installation of Cygwin, plus the cygwin-debuginfo and gdb packages.
That should be enough to get us going.


Thanks,
Corinna


(*) http://msdn.microsoft.com/en-us/library/windows/hardware/ff551063%28v=vs.85%29.aspx
(**) http://download.microsoft.com/download/D/1/A/D1AD0063-7ECE-4589-A846-4971B56AFF09/Windows_winblue.9600.16384.130821-1623.x64fre.Symbols-IRM_SYM_X64FRE_EN-US_MSI.msi


Corinna

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

[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]

Re: find_fast_cwd warning persists after uninstalling (Windows 8.1 x64)

[Mayank Patke]

> 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

Re: find_fast_cwd warning persists after uninstalling (Windows 8.1 x64)

[Corinna Vinschen]

[-- Attachment #1: Type: text/plain, Size: 2656 bytes --]

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.
> 
> 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.
> 
> > 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.
> 
> I'm willing to debug, but I'd need someone to step me through this.
> 
> > 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.
> 
> Still willing to help.
> 
> 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

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

[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]

Re: find_fast_cwd warning persists after uninstalling (Windows 8.1 x64)

[Mayank Patke]

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

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.

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

I'm willing to debug, but I'd need someone to step me through this.

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

Still willing to help.

I'm not sure what level of expertise you're looking for, but I'll do
whatever I can to help get this resolved.

~ Mayank Patke

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

Re: find_fast_cwd warning persists after uninstalling (Windows 8.1 x64)

[Andrey Repin]

Greetings, Mayank Patke!

> I decided to uninstall Cygwin because, frankly, I don't use it that
> much and because the find_fast_cwd warning in the output of certain
> commands has been interfering with other programs which don't expect
> the warning in the output.

> I confirmed that steps 1-3 here
> (http://www.cygwin.com/faq/faq.html#faq.setup.uninstall-all) don't
> apply, then uninstalled all packages via the setup utility. I deleted
> the Cygwin root directory and all shortcuts, although I left the setup
> utility and the downloaded files in my downloads directory for now. I
> checked the registry for all matches for "cyg" and deleted them,
> Software/Cygwin entries in particular, and I have no CYGWIN
> environment variable and PATH does not include the Cygwin directory.

> If I now enter Windows command prompt, commands like "ssh" and
> "cygcheck" are no longer valid and I get the appropriate error
> message. However, if I run commands like "ls" and "make" (included by
> other collections, such as MinGW), I continue to get the find_fast_cwd
> warning.

> I experimented a bit, and running "ls" in PowerShell, where it is a
> built-in alias, does not produce the error message as it does in
> command prompt, where it is not a built-in command. "make" is not
> built in to either one and produces the error message in both
> environments.

> What do I need to do in order to prevent this message from showing up
> again? (Is there some remnant of Cygwin that I still need to remove?)

Since you've removed Cygwin, this is not a Cygwin question.
Neither you provided enough information, such as paths to executables you use,
that produce such messages.
But by the look of it, you were not using Cygwin at all all this time.
So, the problem is not in Cygwin, again.


--
WBR,
Andrey Repin (anrdaemon@yandex.ru) 14.04.2014, <13:10>

Sorry for my terrible english...


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

Re: find_fast_cwd warning persists after uninstalling (Windows 8.1 x64)

[Corinna Vinschen]

[-- Attachment #1: Type: text/plain, Size: 2258 bytes --]

On Apr 14 04:37, Mayank Patke wrote:
> I decided to uninstall Cygwin because, frankly, I don't use it that
> much and because the find_fast_cwd warning in the output of certain
> commands has been interfering with other programs which don't expect
> the warning in the output.

The problem is this:  We don't have a clue under what circumstances
this message is printed.  We know *why* it's printed, but none of
the core maintainers and none of the package maintainers seem to have
a system which suffers from this problem.

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.

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.

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.

But, alas, nobody has offered to help so far.

> However, if I run commands like "ls" and "make" (included by
> other collections, such as MinGW), I continue to get the find_fast_cwd
> warning.

In your MingW environment, you're probably using the tools from MSYS2.
MSYS2 is just a copy of Cygwin with a few tweaks for easier integration
with a native MingW toolchain.  MSYS2 is using the find_fast_cwd code
as well, so you're getting the same warning.

> What do I need to do in order to prevent this message from showing up
> again? (Is there some remnant of Cygwin that I still need to remove?)

The Cygwin remnant is probably MSYS2.  Other than that, if somebody
would take a heart trying to find out what introduced the problem on
his or her machine, we could eventually get rid of it completely.

Corinna

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

[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]

find_fast_cwd warning persists after uninstalling (Windows 8.1 x64)

[Mayank Patke]

I decided to uninstall Cygwin because, frankly, I don't use it that
much and because the find_fast_cwd warning in the output of certain
commands has been interfering with other programs which don't expect
the warning in the output.

I confirmed that steps 1-3 here
(http://www.cygwin.com/faq/faq.html#faq.setup.uninstall-all) don't
apply, then uninstalled all packages via the setup utility. I deleted
the Cygwin root directory and all shortcuts, although I left the setup
utility and the downloaded files in my downloads directory for now. I
checked the registry for all matches for "cyg" and deleted them,
Software/Cygwin entries in particular, and I have no CYGWIN
environment variable and PATH does not include the Cygwin directory.

If I now enter Windows command prompt, commands like "ssh" and
"cygcheck" are no longer valid and I get the appropriate error
message. However, if I run commands like "ls" and "make" (included by
other collections, such as MinGW), I continue to get the find_fast_cwd
warning.

I experimented a bit, and running "ls" in PowerShell, where it is a
built-in alias, does not produce the error message as it does in
command prompt, where it is not a built-in command. "make" is not
built in to either one and produces the error message in both
environments.

What do I need to do in order to prevent this message from showing up
again? (Is there some remnant of Cygwin that I still need to remove?)

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