From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Cc: Niclas Helbig <niclderboss@gmail.com>
Subject: Re: Log.text error
Date: Wed, 2 Feb 2022 22:13:24 -0700 [thread overview]
Message-ID: <f711887e-5d4a-604c-a7aa-94f1bfeaf5ec@SystematicSw.ab.ca> (raw)
In-Reply-To: <CA+ouS39GsEyORHu3SRd_4U49AUY_T5xySpJwLe-=mWbQqf5kSg@mail.gmail.com>
On 2022-02-02 21:34, Niclas Helbig wrote:
> The log Text told me to send you this.
> I am no Code-wizzard, so I dont really know what this means.
>
> I dont have Surface Wind Layer and WAFS Turbulence unfortunatly.
> Would really like to fix that but dont know how.
...
0 [main] WIN32wgrib2 5128 find_fast_cwd: WARNING: Couldn't
compute FAST_CWD pointer. Please report this problem to
the public mailing list cygwin@cygwin.com
328371 [main] WIN32wgrib2 5128 exception::handle: Exception:
STATUS_STACK_OVERFLOW
331088 [main] WIN32wgrib2 5128 open_stackdumpfile: Dumping stack trace
to WIN32wgrib2.exe.stackdump
0 [main] WIN32wgrib2 10104 find_fast_cwd: WARNING: Couldn't
compute FAST_CWD pointer. Please report this problem to
the public mailing list cygwin@cygwin.com
...
Your ancient version of Cygwin is incompatible with your version of
Windows - please update Cygwin:
https://cygwin.com/faq.html#faq.using.fixing-find_fast_cwd-warnings
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in binary units and prefixes, physical quantities in SI.]
prev parent reply other threads:[~2022-02-03 5:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-03 4:34 Niclas Helbig
2022-02-03 5:13 ` Brian Inglis [this message]
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=f711887e-5d4a-604c-a7aa-94f1bfeaf5ec@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--cc=cygwin@cygwin.com \
--cc=niclderboss@gmail.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).