From: Bart Schaefer <schaefer@brasslantern.com>
To: Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: [BUG] With --disable-dynamic-nss, not all functions calls are protected
Date: Thu, 16 Sep 2021 09:48:15 -0700 [thread overview]
Message-ID: <CAH+w=7a1vMadgprg_BzYGajiCHZm1Z_NMGzevKXkEVpg=70aGw@mail.gmail.com> (raw)
In-Reply-To: <20210916121056.p4zainnlnoi74yiw@sym.noone.org>
> > > 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.
> >
> > Probably getrlimit() is implemented by prlimit64() that appears
> > in the strace log, I guess.
Hmm. There are two calls to uname() in the strace. There are only
two places in the source code that might call uname(), both happen via
createparamtable(), and createparamtable() is called from setupvals()
before it calls getrlimit() to populate the limits array. Yet the two
uname() calls are one before prlimit64() and one after, so if prlimit
== getrlimit, I can't find a code flow that matches the order of
events in the strace.
next prev parent reply other threads:[~2021-09-16 16:49 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 [this message]
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=7a1vMadgprg_BzYGajiCHZm1Z_NMGzevKXkEVpg=70aGw@mail.gmail.com' \
--to=schaefer@brasslantern.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).