public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: Previously-functional gawk script now failing to execute - PLEASE HELP!!!
Date: Wed, 15 Sep 2021 19:58:47 -0600	[thread overview]
Message-ID: <2ecc9f97-4324-2948-5e6b-1fffa72b2d27@SystematicSw.ab.ca> (raw)
In-Reply-To: <CAC7Qdh0tn4L9BzvRV6xKXaB6EUMRjPWLsaoK=bVdphfJa6NKiQ@mail.gmail.com>

On 2021-09-15 15:11, Bryan VanSchouwen via Cygwin wrote:
> I just tried executing an old, previously-functional awk script using a
> version of gawk that I had downloaded last year, and a command of the
> following format (as recommended in a previous communication with the
> Cygwin mailing list):
> gawk -vRS="\r\n" -f data_collect_e_-_FF_4-state.awk
> but this time, the script failed to execute!!
> 
> Upon closer examination, the script appears to be failing after
> successfully reading the first line of data from the input data file, even
> though the input file has NOT been modified since it was last used.  (I
> should point out that while the files were copied over from my old
> computer, another awk script execution that I had attempted recently with
> older files worked fine!)

So the script is not failing to execute, it is successfully reading the 
first line: so how is it failing, and what has that to do with the input 
file being modified, and if the input file has not been modified since 
the script was last used, why are you rerunning it?

Package gawk has been updated once a year for the last 4 years, up until 
2020-04, and has not changed recently, so the problem may be with your 
data file, or the script, or your Cygwin installation, and only you can 
really answer that, as they have been "copied" from another computer: 
using what process? How was Cygwin setup on the new computer, and which 
version of gawk was installed to be used?

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

  parent reply	other threads:[~2021-09-16  1:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-15 21:11 Bryan VanSchouwen
2021-09-15 21:33 ` Bill Stewart
2021-09-15 21:43 ` Eliot Moss
2021-09-16  1:58 ` Brian Inglis [this message]
2021-09-15 23:01 Bryan VanSchouwen
2021-09-15 23:49 ` Lee

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=2ecc9f97-4324-2948-5e6b-1fffa72b2d27@SystematicSw.ab.ca \
    --to=brian.inglis@systematicsw.ab.ca \
    --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).