From: Stefano Brivio <sbrivio@redhat.com>
To: Yumei Huang <yuhuang@redhat.com>
Cc: passt-dev@passt.top, david@gibson.dropbear.id.au
Subject: Re: [PATCH] test: Fix printf error when debug is enabled
Date: Tue, 30 Sep 2025 00:24:17 +0200 [thread overview]
Message-ID: <20250930002417.55172be7@elisabeth> (raw)
In-Reply-To: <20250929063014.17293-1-yuhuang@redhat.com>
On Mon, 29 Sep 2025 14:30:14 +0800
Yumei Huang <yuhuang@redhat.com> wrote:
> Running test pasta/tcp with debug enabled would get stuck with
> below error:
>
> + printf 'DEBUG: ns socat -u OPEN:__BASEPATH__/big.bin TCP6:[__GW6__%__IFNAME__]:10003\n'
> lib/term: line 38: printf: `_': invalid format character
>
> The error occurs because printf interprets the % character as the
> start of a format specifier, and the following '_' isn't one of
> them.
>
> Fix it by replacing 'printf "${*}\n"' with 'printf "%s\n" "$*"'.
I'm not sure why, but this breaks colour highlights for me. Instead of
seeing a part of this message in blue, now I get:
Test layout: \033[1;34msingle passt instance with guest\033[0m.\n
I can look into it if it only happens for me, or if needed.
By the way (I'm not sure if it's related), I used curly brackets
everywhere to unambiguously distinguish names of variables, and '*' is
a name.
The curly brackets are almost always optional, see POSIX.1-2024 for the
cases where they are needed:
https://pubs.opengroup.org/onlinepubs/9699919799/utilities/V3_chap02.html#tag_18_06_02
...to avoid possible issues, I just used them everywhere, and I think
it would be good to keep this consistent. That is, the $* should remain
as ${*}.
--
Stefano
next prev parent reply other threads:[~2025-09-29 22:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-29 6:30 Yumei Huang
2025-09-29 6:41 ` David Gibson
2025-09-29 22:24 ` Stefano Brivio [this message]
2025-09-30 0:23 ` David Gibson
2025-09-30 1:32 ` Yumei Huang
2025-09-30 11:13 ` Stefano Brivio
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=20250930002417.55172be7@elisabeth \
--to=sbrivio@redhat.com \
--cc=david@gibson.dropbear.id.au \
--cc=passt-dev@passt.top \
--cc=yuhuang@redhat.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.
Code repositories for project(s) associated with this public inbox
https://passt.top/passt
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 IMAP folder(s).