From: Bruce Jerrick <bmj001@gmail.com>
To: cygwin@cygwin.com
Subject: xargs completely broken under cygwin 3.6.0-0.108.gb7f5a33200a9
Date: Mon, 1 Apr 2024 20:36:15 -0700 [thread overview]
Message-ID: <a40780cc-82d1-4d00-7fa0-e11c9b1a96a1@gmail.com> (raw)
'xargs' (part of 'findutils') is completely broken if
3.6.0-0.108.gb7f5a33200a9 (test version) is installed:
$ xargs
xargs: Unexpected suffix cmdline on cmdline
$ xargs --version
xargs: Unexpected suffix cmdline on cmdline
$ echo narf | xargs echo
xargs: Unexpected suffix cmdline on cmdline
'xargs' is from the current x86_64 findutils-4.9.0-1 .
All other packages are up to date per setup.ini dated
2024-04-01 21:32:37 GMT.
I first discovered this under Windoze 11 Insider Preview
(with no other Cygwin test versions).
On a Windoze 10 machine, it was OK with cygwin 3.5.1-1,
appeared when I installed 3.6.0-0.108.gb7f5a33200a9,
then went away when I reverted to 3.5.1-1 .
(All machines are VMware VM's.)
----------------------------------------------------------------
I have just started looking at the source, and the error
is coming from this snippet from 'safe_atoi()' in
lib/safe-atoi.c :
safe_atoi (const char *s, enum quoting_style style)
{
...
lval = strtol (s, &end, 10);
...
else if (*end)
{
die (EXIT_FAILURE, errno, _("Unexpected suffix %s on %s"),
quotearg_n_style (0, style, end),
quotearg_n_style (1, style, s));
}
...
From 'man 3 strtol":
"If the subject string is empty (or not in acceptable form),
no conversion is performed and the value of s is stored
in ptr [i.e., 'end'] ..."
Which is apparently what is happening here.
I have yet to discover where "cmdline" is coming from (perhaps
/proc/%d/cmdline), let alone what it looks like.
Further progress by me will depend on what success I have in
building 'findutils' from source :) .
next reply other threads:[~2024-04-02 3:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-02 3:36 Bruce Jerrick [this message]
2024-04-02 6:18 ` Brian Inglis
2024-04-02 7:48 ` Bruce Jerrick
2024-04-02 8:08 ` Bruce Jerrick
2024-04-02 8:42 ` Bruce Jerrick
2024-04-02 10:44 ` Corinna Vinschen
2024-04-02 13:13 ` Corinna Vinschen
2024-04-02 15:38 ` Bruce Jerrick
2024-04-02 18:33 ` Corinna Vinschen
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=a40780cc-82d1-4d00-7fa0-e11c9b1a96a1@gmail.com \
--to=bmj001@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).