public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Peter Rallis <rallis.petros@gmail.com>
To: cygwin@cygwin.com
Subject: Re: weatherServerLog xplane11
Date: Fri, 27 May 2022 20:34:39 +0300	[thread overview]
Message-ID: <CABmMDRtx2Yh-A5HcLEf4n+w14fEU-UFN+t3HzWZVqJ9PxH_GKQ@mail.gmail.com> (raw)
In-Reply-To: <CA+kUOam68JEMhoqdVBM6Pnq2onRkg_d++wQ1Akzfpr4LjZDndg@mail.gmail.com>

Thank you for the information Adam.

Στις Παρ 27 Μαΐ 2022 στις 8:32 μ.μ., ο/η Adam Dinwoodie <adam@dinwoodie.org>
έγραψε:

> On Fri, 27 May 2022 at 17:27, Peter Rallis <rallis.petros@gmail.com>
> wrote:
> >
> > Good evening
> >
> > I Have the below message in xplane 11  in NOAA Weather
> >
> > 1 [main] WIN32wgrib2 8852 find_fast_cwd: WARNING: Couldn't compute
> FAST_CWD
> > pointer.  Please report this problem to
> > the public mailing list cygwin@cygwin.com
> >  950412 [main] WIN32wgrib2 8852 exception::handle: Exception:
> > STATUS_STACK_OVERFLOW
> >  952427 [main] WIN32wgrib2 8852 open_stackdumpfile: Dumping stack trace
> to
> > WIN32wgrib2.exe.stackdump
> >       1 [main] WIN32wgrib2 3508 find_fast_cwd: WARNING: Couldn't compute
> > FAST_CWD pointer.  Please report this problem to
> > the public mailing list cygwin@cygwin.com
> >
> > Thank you
>
> Hi Peter,
>
> Please see
> https://cygwin.com/faq/faq.html#faq.using.fixing-find_fast_cwd-warnings
> for more information on this error. In short, it indicates whoever you
> got that software from is using a very old version of Cygwin, and you
> need to ask them to fix this.
>
> Adam
>


-- 

*Kind RegardsP.Rallis*

  reply	other threads:[~2022-05-27 17:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-27 16:26 Peter Rallis
2022-05-27 17:32 ` Adam Dinwoodie
2022-05-27 17:34   ` Peter Rallis [this message]
2022-06-05 11:54 ` cygwinautoreply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CABmMDRtx2Yh-A5HcLEf4n+w14fEU-UFN+t3HzWZVqJ9PxH_GKQ@mail.gmail.com \
    --to=rallis.petros@gmail.com \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).