public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Mark Geisert <mark@maxrnd.com>
To: cygwin@cygwin.com
Subject: Re: cat.exe failing silently with exit status 3
Date: Wed, 27 Mar 2019 04:21:00 -0000	[thread overview]
Message-ID: <e31c8baa-43ab-e59f-91e9-86c8c66e40df@maxrnd.com> (raw)
In-Reply-To: <f1b4552855e64297f37f0c41203a8ad4@plebeian.com>

Chris Wagner wrote:
> Hi all.  A few days ago I noticed that cat.exe was failing without printing any
> output or errors and exiting with status 3.  I tried rebooting, updating my
> Cygwin, even a fresh install of Base only.  I removed all recently installed
> Windows software and nothing changed.  What's truly strange is that it seems to
> be only cat that is broken.  Hilariously tac works fine.  I can even emulate cat
> with "tac foo |tac".
>
> Whatever changed, Cygwin, coreutils, or Windows, I can't narrow it down.  I'm on
> Windows 7 SP1 and my Cygwin is up to date (3.0.4-1).  Coreutils is 8.26-2.
>
> I launched cat with strace and it always ends with:
> --- Process 3928, exception c0000005 at 0000000000000000
> --- Process 3928 thread 10476 exited with status 0xc0000001
> --- Process 3928 exited with status 0xc0000001
>
> The output is vastly truncated compared to what tac shows.  The thread dies
> immediately instead of loading the environment, etc.
>
> I attached the strace output of cat and tac along with the sysinfo and cygcheck
> output.  I hope this is just something simple overlooked in the latest version
> of cat.

Hi Chris,
This bit of text from your strace...

Cygwin WARNING:
   Couldn't compute FAST_CWD pointer.  This typically occurs if you're using
   an older Cygwin version on a newer Windows.  Please update to the latest
   available Cygwin version from https://cygwin.com/.  If the problem persists,
   please see https://cygwin.com/problems.html

...shows that somehow you're involving an old cygwin1.dll version.  For just 
'cat', which is indeed puzzling.  Check your PATH variable to make sure you 
don't have some other environment (containing an old Cygwin) that supplies cat 
before Cygwin's cat.  Maybe also do 'cygcheck -svr' and see whether it finds 
more than one Cygwin installation on your system.  Do you have an alias for 
'cat' that does something complicating?

..mark


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

  parent reply	other threads:[~2019-03-27  4:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-27  3:55 Chris Wagner
2019-03-27  4:19 ` Doug Henderson
2019-03-27  4:21 ` Mark Geisert [this message]
2019-03-27  4:39 ` Brian Inglis
2019-03-27 16:40 ` Chris Wagner

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=e31c8baa-43ab-e59f-91e9-86c8c66e40df@maxrnd.com \
    --to=mark@maxrnd.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).