From: Jakub Jelinek <jakub@redhat.com>
To: Florian Weimer <fweimer@redhat.com>
Cc: "H.J. Lu" <hjl.tools@gmail.com>, libc-alpha@sourceware.org
Subject: Re: [PATCH] tst-tls6.sh: Replace space with ':' in LD_PRELOAD
Date: Tue, 6 Feb 2024 15:02:38 +0100 [thread overview]
Message-ID: <ZcI7/nqXGM0DX50f@tucnak> (raw)
In-Reply-To: <874jelhevn.fsf@oldenburg.str.redhat.com>
On Tue, Feb 06, 2024 at 03:00:12PM +0100, Florian Weimer wrote:
> * H. J. Lu:
>
> > Replace space with ':' in LD_PRELOAD. This fixes [BZ #31344].
>
> I think the test currently passes because we use an ELF constructor in
> the LD_PRELOAD module to register test cases. So we just lose some test
> coverage by ignoring the LD_PRELOAD modules. In other cases we rely on
> explicit symbol bindings/lookups to make sure that everythin has been
> loaded as expected. But as a minimal fix, this looks okay.
>
> Regarding the actual change:
>
> LD_PRELOAD="`echo ${common_objpfx}nptl/tst-tls5mod{$aligned,b,c,d}.so \
> + | sed 's/:$//;s/: /:/g;s/ /:/g'`" ${tst_tls5} >> $logfile \
> + || fail=1
>
> I believe this could be:
>
> + LD_PRELOAD="`echo ${common_objpfx}nptl/tst-tls5mod{$aligned,b,c,d}.so \
> + | tr ' ' :`" ${tst_tls5} >> $logfile || fail=1
>
> You could use set -- and IFS, but that's probably too obscure.
At least ld.so manpage documents for LD_PRELOAD:
"The items of the list can be separated by spaces or colons, and there is no
support for escaping either separator."
So, is that not true?
Jakub
next prev parent reply other threads:[~2024-02-06 14:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-06 12:42 H.J. Lu
2024-02-06 12:58 ` Andreas Schwab
2024-02-06 13:11 ` H.J. Lu
2024-02-06 13:17 ` Andreas Schwab
2024-02-06 14:00 ` Florian Weimer
2024-02-06 14:02 ` Jakub Jelinek [this message]
2024-02-06 14:10 ` Adhemerval Zanella Netto
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=ZcI7/nqXGM0DX50f@tucnak \
--to=jakub@redhat.com \
--cc=fweimer@redhat.com \
--cc=hjl.tools@gmail.com \
--cc=libc-alpha@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).