From: Tom de Vries <tdevries@suse.de>
To: gdb-patches@sourceware.org
Subject: Re: [PATCH v2 0/3] [gdb] Three gdb_buildall.sh fixes
Date: Mon, 14 Sep 2026 23:32:47 +0200 [thread overview]
Message-ID: <c06117e1-bae8-439c-a9c7-5a2c7b7f7e8f@suse.de> (raw)
In-Reply-To: <20260831074155.3500918-1-tdevries@suse.de>
On 8/31/26 9:41 AM, Tom de Vries wrote:
> This series contains three patches related to gdb/gdb_buildall.sh.
>
> The first fixes an error.
>
> The second fixes a warning.
>
> The last makes it shellcheck-clean.
>
> Tested on aarch64-linux by running:
> ...
> $ rm -Rf build-all
> $ mkdir build-all
> $ bash ./src/gdb/gdb_buildall.sh \
> -j 9 \
> --bfd64 \
> src \
> build-all
> ...
>
I've pushed this series.
Thanks,
- Tom
> Changes in v2:
> - in the third patch, use array for targexp handling to fix bug where we get
> grep "-e foo -e bar"
> - in the third patch, remove useless cat
>
> Versions:
> - v1 https://sourceware.org/pipermail/gdb-patches/2026-August/229841.html
>
> Tom de Vries (3):
> [gdb] Use --data-directory in gdb_buildall.sh
> [gdb] Fix warnings in gdb_buildall.sh
> [gdb] Make gdb_buildall.sh shellcheck-clean
>
> gdb/contrib/shellcheck.sh | 1 -
> gdb/gdb_buildall.sh | 88 +++++++++++++++++++++------------------
> 2 files changed, 47 insertions(+), 42 deletions(-)
>
>
> base-commit: bcdc54fb7a34a312777fa814e065b2cc01424e0a
prev parent reply other threads:[~2026-09-14 21:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-31 7:41 Tom de Vries
2026-08-31 7:41 ` [PATCH v2 1/3] [gdb] Use --data-directory in gdb_buildall.sh Tom de Vries
2026-08-31 7:41 ` [PATCH v2 2/3] [gdb] Fix warnings " Tom de Vries
2026-08-31 7:41 ` [PATCH v2 3/3] [gdb] Make gdb_buildall.sh shellcheck-clean Tom de Vries
2026-09-14 21:32 ` Tom de Vries [this message]
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=c06117e1-bae8-439c-a9c7-5a2c7b7f7e8f@suse.de \
--to=tdevries@suse.de \
--cc=gdb-patches@sourceware.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