zsh-workers
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: Zsh hackers list <zsh-workers@zsh.org>, 993843@bugs.debian.org
Subject: Re: [BUG] With --disable-dynamic-nss, not all functions calls are protected
Date: Wed, 15 Sep 2021 12:13:31 -0700	[thread overview]
Message-ID: <CAH+w=7aScd=FUM3f03fhBSyi5hqdt1_Y+Z95_bf2LOT-wr9RWA@mail.gmail.com> (raw)
In-Reply-To: <20210915143102.pw5uup7bvufi7wse@sym.noone.org>

On Wed, Sep 15, 2021 at 7:32 AM Axel Beckert <abe@debian.org> wrote:
>
> But copying zsh-static on a system with a different libc6 version
> still segfaults, so this patch might be necessary but not sufficient.
>
> Last line is:
>
>   zsh-static: dl-call-libc-early-init.c:37: _dl_call_libc_early_init: Assertion `sym != NULL' failed.

Based on the strace, my guess would be that getrlimit() is what's
attempting to link to the dynamic library.  This is based on the
success of the uname() call and on what does NOT appear in the
subsequent trace output.  If getrlimit() does have this effect, it's
possible that getrusage() will as well.


  reply	other threads:[~2021-09-15 19:14 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 [this message]
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
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='CAH+w=7aScd=FUM3f03fhBSyi5hqdt1_Y+Z95_bf2LOT-wr9RWA@mail.gmail.com' \
    --to=schaefer@brasslantern.com \
    --cc=993843@bugs.debian.org \
    --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).