From: Pedro Alves <pedro@palves.net>
To: Andrew Burgess <aburgess@redhat.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb/Windows testsuite: Avoid "bad" words in exe names
Date: Fri, 10 Jul 2026 20:14:16 +0100 [thread overview]
Message-ID: <1d43eb59-09e9-49ef-9a53-4c6d0d983117@palves.net> (raw)
In-Reply-To: <874ii6gb4c.fsf@redhat.com>
Hi Andrew,
On 2026-07-10 15:41, Andrew Burgess wrote:
> The change looks fine, but I wonder if we should factor this mapping
> into a helper function? There are tests that setup multiple
> executables, and a common pattern is to call standard_output_file rather
> than building the names from BINFILE. It might be helpful if we had a
> helper proc that we could call if needed in these cases.
>
> Or maybe standard_output_file could use parse_some_args to allow
> something like:
>
> set binfile [standard_output_file -exec ${binfile_basename}]
>
> with '-exec' being a flag to indicate we're creating an executable, in
> which ase BINFILE_BASENAME would have the string mapping applied?
>
> Just a thought though, we can always tweak things later if you'd rather
> stick with this.
>
Yeah, this approach has some fragility to it. I just now sent an alternative
approach, based on embedding a manifest into the test executables:
https://inbox.sourceware.org/gdb-patches/17aacd11-cc42-43eb-8328-bdcedcc0dfb5@palves.net/
That should be more robust, and let us not have to worry about this ever again (fingers crossed).
> Reviewed-By: Andrew Burgess <aburgess@redhat.com>
Thank you.
Pedro Alves
prev parent reply other threads:[~2026-07-10 19:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-09 17:43 Pedro Alves
2026-07-10 5:18 ` Eli Zaretskii
2026-07-10 18:59 ` [PATCH] gdb/Windows testsuite: Embed asInvoker manifest in test executables Pedro Alves
2026-07-10 19:09 ` Pedro Alves
2026-07-11 6:07 ` Eli Zaretskii
2026-07-22 14:16 ` Pedro Alves
2026-07-10 14:41 ` [PATCH] gdb/Windows testsuite: Avoid "bad" words in exe names Andrew Burgess
2026-07-10 19:14 ` Pedro Alves [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=1d43eb59-09e9-49ef-9a53-4c6d0d983117@palves.net \
--to=pedro@palves.net \
--cc=aburgess@redhat.com \
--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