Your Cygwin version does not support your Windows version:
you must upgrade Cygwin and all packages using Cygwin setup;
see:
https://cygwin.com/faq.html#faq.using.fixing-find_fast_cwd-warnings
and choose:
https://cygwin.com/setup-x86_64.exe
or:
https://cygwin.com/setup-x86.e
n.com
Subject: [EXTERNAL] Re: Find_fast_cwd : warning
>Hello team,
>I am facing below warning many times when I am using
>cygwin\lib\gcc\i686-pc-cygwin\4.8.3 ..please do me know what is the
>solution for this issue
>1 [main] sh 18352 find_fast_cwd: WARNING: Couldn't compute FA
>Hello team,
>I am facing below warning many times when I am using
>cygwin\lib\gcc\i686-pc-cygwin\4.8.3 ..please do me know what is the solution
>for this issue
>1 [main] sh 18352 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer.
>Please report this problem to
>the public mailing li
On 2018-05-05 12:10, Maxime M wrote:
> This is very strange, I downloaded johntheripper from the official website
> and I get this error:
> 1 [main] john 10244 find_fast_cwd: WARNING: Couldn't compute FAST_CWD
> pointer. Please report this problem to
> the public mailing list cygwin@cygwin.com
>
On 7/30/2015 1:43 AM, rob_mcallis...@keysight.com wrote:
To who it may concern,
I am seeing several of these "Couldn't compute FAST_CWD pointer" warnings
I am compiling an R package. I am using R version 2.15.1 and Rtools version
2.15.0.1919
Rtools includes Cygwin
My build system is Windows Se
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
> 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 sym
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 l
> 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
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, alt
> 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 un
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 her
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:
13 matches
Mail list logo