unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Jan D." <jan.h.d@swipnet.se>
Cc: emacs-devel@gnu.org
Subject: Re: `exec shield' test in configure too strict?
Date: Wed, 20 Oct 2004 22:33:16 +0200	[thread overview]
Message-ID: <457CE2D6-22D7-11D9-BDB3-000D93505B76@swipnet.se> (raw)
In-Reply-To: <E1CHISk-0003NI-Iu@fencepost.gnu.org>


>> Another idea: can `main' contain code to move its heap address to the
>> desired place, at startup?
>
>     No, as the desired place is not a mapped memory region, you can 
> not write
>     there.
>
> How about mapping a memory region at the desired place, then
> putting the heap address there?

It could work, but sounds tricky, you would have to mmap exactly
between BSS and the heap.  It is possible that the kernel could
reject such a request.  I haven't tested it though.

>       But we could do as described by Camm Maguire, check if the heap 
> is not
>     at the correct place at temacs startup, and if it is not, call
>     personality(LINUX32) and exec() temacs again.
>
> That also seems like a good method, perhaps better.  It would require
> testing whether the symbols pertaining to personalites are developed,
> but that is a test done by compilation, so it should be 
> unproblematical.

I have checked in this method now.  I actually have an unexelf.c that 
works
with exec-shield on now, but I have only tested it on Fedora Core 2.  It
is probably too risky to check it in this close to a release.

	Jan D.

  reply	other threads:[~2004-10-20 20:33 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
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. [this message]
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=457CE2D6-22D7-11D9-BDB3-000D93505B76@swipnet.se \
    --to=jan.h.d@swipnet.se \
    --cc=emacs-devel@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).