From: Keith Seitz <keiths@redhat.com>
To: Sam James <sam@gentoo.org>, gdb-patches@sourceware.org
Subject: Re: [PATCH 2/2] gdb-add-index: fix shellcheck warnings
Date: Sat, 29 Mar 2025 16:42:57 -0700 [thread overview]
Message-ID: <2aef1e6c-ab5d-4884-8de2-0073ace3e194@redhat.com> (raw)
In-Reply-To: <0fa2e0d207eef78dc6a4305ee28588676932753e.1743188332.git.sam@gentoo.org>
Hi,
On 3/28/25 11:58 AM, Sam James wrote:
> * Drop useless echo
> * Add missing quoting to rm argument (and use -- to delimit options)
> * Fix quoting w/ trap to avoid expanding $tmp_files immediately
Again, thank you for doing this.
> ---
> gdb/contrib/gdb-add-index.sh | 7 +++----
> 1 file changed, 3 insertions(+), 4 deletions(-)
>
> diff --git a/gdb/contrib/gdb-add-index.sh b/gdb/contrib/gdb-add-index.sh
> index b299f830373..f727d28aac7 100755
> --- a/gdb/contrib/gdb-add-index.sh
> +++ b/gdb/contrib/gdb-add-index.sh
> @@ -163,10 +162,10 @@ for f in "$file" "$dwz_file"; do
> tmp_files="$tmp_files $index4 $index5 $debugstr $debugstrmerge $debugstrerr"
> done
>
> -rm -f $tmp_files
> +rm -f -- "$tmp_files"
By preventing expansion, wouldn't this be attempting to
erase a single file whose name is a concatenation of all the
temporary files?
That is,
$ touch a b c
$ tmp="a b c"
$ rm -- "$tmp"
rm: cannot remove 'a b c': No such file or directory
Keith
next prev parent reply other threads:[~2025-03-29 23:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-28 18:58 [PATCH 0/2] shell fixes for gcore, gdb-add-index Sam James
2025-03-28 18:58 ` [PATCH 1/2] gcore: improve shell use Sam James
2025-03-29 23:42 ` Keith Seitz
2025-03-31 18:26 ` Simon Marchi
2025-03-31 18:44 ` Andreas Schwab
2025-03-31 18:54 ` Simon Marchi
2025-04-02 16:08 ` Keith Seitz
2025-04-01 13:39 ` Tom Tromey
2025-04-02 16:15 ` Simon Marchi
2025-04-02 20:31 ` Tom Tromey
2025-03-28 18:58 ` [PATCH 2/2] gdb-add-index: fix shellcheck warnings Sam James
2025-03-29 23:42 ` Keith Seitz [this message]
2025-03-31 18:30 ` Simon Marchi
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=2aef1e6c-ab5d-4884-8de2-0073ace3e194@redhat.com \
--to=keiths@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=sam@gentoo.org \
/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