From: Roman Perepelitsa <roman.perepelitsa@gmail.com>
To: Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: [BUG] With --disable-dynamic-nss, not all functions calls are protected
Date: Fri, 17 Sep 2021 15:55:43 +0200 [thread overview]
Message-ID: <CAN=4vMqGT9f6E8Q3-PNt5BvQ92hoae4QkDDkFBmeu8zXbbWPYw@mail.gmail.com> (raw)
In-Reply-To: <20210917134439.l7yxmbp4ewajvjau@sym.noone.org>
On Fri, Sep 17, 2021 at 3:45 PM Axel Beckert <abe@deuxchevaux.org> wrote:
>
> Hi,
>
> On Fri, Sep 17, 2021 at 05:45:37PM +0900, Jun T wrote:
> > > I guess the problem is getlogin() called from createparamtable().
> >
> > Yes, this can be confirmed by statically linking a test program
> > (just call getlogin() and exit). I _hope_ there are no other places
> > where NSS-functions are indirectly called.
> >
> > Revised the Axel's patch (also attached a file):
>
> Yay, this patch works for me! zsh-static built on Debian Unstable
> (glibc 2.32) no more segfaults when copied to and executed on Debian
> 11 Bullseye (glibc 2.31) for me.
If your goal is to create a binary that runs on any Linux x64 box
regardless of libc runtimes that may or may not be available on it,
link against musl libc. Static linking against glibc is a lost cause.
Zsh can link against musl libc out of the box. This is how I build
mine.
Roman.
next prev parent reply other threads:[~2021-09-17 13:56 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-08 1:12 Vincent Lefevre
2021-09-15 14:31 ` Axel Beckert
2021-09-15 19:13 ` Bart Schaefer
2021-09-16 7:37 ` Jun T
2021-09-16 12:10 ` Axel Beckert
2021-09-16 16:48 ` Bart Schaefer
2021-09-16 18:21 ` Jun. T
2021-09-16 18:34 ` Axel Beckert
2021-09-16 22:01 ` Bart Schaefer
2021-09-17 1:23 ` Jun T
2021-09-17 8:45 ` Jun T
2021-09-17 13:44 ` Axel Beckert
2021-09-17 13:55 ` Roman Perepelitsa [this message]
2021-09-17 14:16 ` Axel Beckert
2021-09-17 15:02 ` Bart Schaefer
2021-09-21 0:53 ` Jun T
2021-09-21 3:38 ` Bart Schaefer
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='CAN=4vMqGT9f6E8Q3-PNt5BvQ92hoae4QkDDkFBmeu8zXbbWPYw@mail.gmail.com' \
--to=roman.perepelitsa@gmail.com \
--cc=zsh-workers@zsh.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
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).