From: Kamil Dudka <kdudka@redhat.com>
To: Oliver Kiddle <okiddle@yahoo.co.uk>
Cc: zsh-workers@zsh.org
Subject: Re: [PATCH 1/2] report bad ELF interpreter if it causes exec to fail
Date: Fri, 17 Apr 2015 17:59:04 +0200 [thread overview]
Message-ID: <2127409.yB077Jb7Wn@kdudka.brq.redhat.com> (raw)
In-Reply-To: <30591.1429284100@thecus.kiddle.eu>
On Friday 17 April 2015 17:21:40 Oliver Kiddle wrote:
> This behaviour got mentioned on one of the blogs that I tend to read
> here:
>
> http://utcc.utoronto.ca/~cks/space/blog/unix/BashSuperintelligentExec
>
> I would agree with the conclusion of that blog writer that this is going
> a little bit overboard.
>
> Also, I'm fairly sure that this would require linking with libelf on
> some systems which is an added dependency.
>
> Oliver
Why would the patch require linking with libelf?
The patch does not rely on any symbols provided by the libelf library. It
just optionally uses <elf.h> if the header file is available during build.
Kamil
next prev parent reply other threads:[~2015-04-17 15:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-17 13:25 Kamil Dudka
2015-04-17 13:25 ` [PATCH 2/2] clear the heredoc list in case par_event() fails Kamil Dudka
2015-04-17 19:17 ` Peter Stephenson
2015-04-20 8:48 ` Kamil Dudka
2018-11-29 16:24 ` Kamil Dudka
2018-11-29 17:34 ` Peter Stephenson
2018-11-29 18:39 ` Bart Schaefer
2018-11-30 9:55 ` Peter Stephenson
2018-11-30 12:53 ` Kamil Dudka
2015-04-17 13:49 ` [PATCH 1/2] report bad ELF interpreter if it causes exec to fail Daniel Shahaf
2015-04-17 14:32 ` Kamil Dudka
2015-04-17 15:21 ` Oliver Kiddle
2015-04-17 15:59 ` Kamil Dudka [this message]
2015-04-17 19:59 ` Oliver Kiddle
2015-04-17 15:41 ` Philippe Troin
2015-04-17 15:51 ` 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=2127409.yB077Jb7Wn@kdudka.brq.redhat.com \
--to=kdudka@redhat.com \
--cc=okiddle@yahoo.co.uk \
--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).