From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Arkadiusz Drabczyk <arkadiusz@drabczyk.org>
Cc: mtk.manpages@gmail.com, linux-man@vger.kernel.org
Subject: Re: [PATCH] ld.so.8: Explain than empty entry in LD_LIBRARY_PATH means cwd
Date: Thu, 25 Jun 2020 09:16:10 +0200 [thread overview]
Message-ID: <856b0c96-f641-dda3-cfaa-57444b7c561b@gmail.com> (raw)
In-Reply-To: <20200623225910.1008-1-arkadiusz@drabczyk.org>
Hello Arkadiusz
On 6/24/20 12:59 AM, Arkadiusz Drabczyk wrote:
> If this was ever going to change the test case is very simple:
>
> /tmp $ touch libc.so.6
> /tmp $ LD_LIBRARY_PATH=: sh
> sh: error while loading shared libraries: libc.so.6: file too short
>
> Signed-off-by: Arkadiusz Drabczyk <arkadiusz@drabczyk.org>
Thanks for the patch, and the succinct test/demo in the commit
message!
Patch applied.
Cheers,
Michael
> ---
> man8/ld.so.8 | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/man8/ld.so.8 b/man8/ld.so.8
> index 9034612..2e98b7f 100644
> --- a/man8/ld.so.8
> +++ b/man8/ld.so.8
> @@ -319,6 +319,7 @@ A list of directories in which to search for
> ELF libraries at execution time.
> The items in the list are separated by either colons or semicolons,
> and there is no support for escaping either separator.
> +A zero-length directory name indicates the current working directory.
> .IP
> This variable is ignored in secure-execution mode.
> .IP
>
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
prev parent reply other threads:[~2020-06-25 7:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-23 22:59 [PATCH] ld.so.8: Explain than empty entry in LD_LIBRARY_PATH means cwd Arkadiusz Drabczyk
2020-06-25 7:16 ` Michael Kerrisk (man-pages) [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=856b0c96-f641-dda3-cfaa-57444b7c561b@gmail.com \
--to=mtk.manpages@gmail.com \
--cc=arkadiusz@drabczyk.org \
--cc=linux-man@vger.kernel.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 NNTP newsgroup(s).