From: Camm Maguire <camm@enhanced.com>
Cc: Eli Zaretskii <eliz@gnu.org>,
emacs-devel@gnu.org, gcl-devel@gnu.org, miles@gnu.org
Subject: Re: `exec shield' test in configure too strict?
Date: 07 Oct 2004 11:44:48 -0400 [thread overview]
Message-ID: <54acuyfs7j.fsf@intech19.enhanced.com> (raw)
In-Reply-To: <437506D2-178C-11D9-BCD2-000D93505B76@swipnet.se>
Greetings!
"Jan D." <jan.h.d@swipnet.se> writes:
> >> I have checked in a test that runs a program and sees if the heap
> >> start
> >> address is random.
> >
> > Doesn't this harm cross-building Emacs? I always thought that running
> > a test program at configure time should be avoided, and that tests
> > that only compile or link programs should be peferred.
>
> When cross compiling the test obviously can not be run, so configure
> assumes
> that the heap start address is not random. Come to think of it, the old
> test (checking /proc/sys/kernel/exec-shield) was worse, as it did not
> handle
> cross compiling.
>
GCL also checks for a randomized sbrk a configure time, and builds
into main a personality switch followed by a re-exec to work around
the fedora security issues. I'm hoping this avenue won't be going
away soon, as I feel there are benefits to the current sbrk-expanding
contiguous heap design of these systems.
Don't know if there is any answer to the cross-compiling.
Take care,
> Jan D.
>
>
>
> _______________________________________________
> Emacs-devel mailing list
> Emacs-devel@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-devel
>
>
>
--
Camm Maguire camm@enhanced.com
==========================================================================
"The earth is but one country, and mankind its citizens." -- Baha'u'llah
next prev parent reply other threads:[~2004-10-07 15:44 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-04 5:53 `exec shield' test in configure too strict? Miles Bader
2004-10-04 15:04 ` Jan D.
2004-10-04 21:20 ` Miles Bader
2004-10-04 21:37 ` Jan D.
2004-10-05 20:40 ` Jan D.
2004-10-05 21:44 ` Stefan Monnier
2004-10-05 22:11 ` Jan D.
2004-10-06 0:18 ` Stefan
2004-10-06 1:34 ` Miles Bader
2004-10-06 7:50 ` Jan D.
2004-10-06 7:56 ` Miles Bader
2004-10-06 11:31 ` Jan D.
2004-10-06 7:48 ` Jan D.
2004-10-06 12:58 ` Stefan Monnier
2004-10-06 11:16 ` Eli Zaretskii
2004-10-06 11:38 ` Jan D.
2004-10-07 15:44 ` Camm Maguire [this message]
2004-10-07 16:44 ` Richard Stallman
2004-10-07 18:16 ` Jan D.
2004-10-09 1:25 ` Richard Stallman
2004-10-11 10:30 ` Jan D.
2004-10-12 8:56 ` Richard Stallman
2004-10-20 20:33 ` Jan D.
2004-10-21 13:57 ` Richard Stallman
2004-10-22 21:02 ` Camm Maguire
2004-10-25 19:05 ` Jan D.
2004-10-26 20:24 ` Camm Maguire
2004-10-27 10:48 ` Richard Stallman
2004-10-27 12:17 ` Jan D.
2004-11-06 17:00 ` other unexec problems Camm Maguire
2004-11-09 7:58 ` Jan D.
2004-10-05 18:04 ` `exec shield' test in configure too strict? Richard Stallman
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=54acuyfs7j.fsf@intech19.enhanced.com \
--to=camm@enhanced.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=gcl-devel@gnu.org \
--cc=miles@gnu.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.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).