unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Jan D." <jan.h.d@swipnet.se>
Cc: rms@gnu.org, gcl-devel@gnu.org, emacs-devel@gnu.org
Subject: Re: other unexec problems
Date: Tue, 9 Nov 2004 08:58:44 +0100	[thread overview]
Message-ID: <2D5E0BD2-3225-11D9-8E4D-000D93505B76@swipnet.se> (raw)
In-Reply-To: <54vfcihq07.fsf_-_@intech19.enhanced.com>

> Greetings!  Two other unexec issues I thought I'd mention in case they
> trigger any ideas:
>
> 1) Unexec'ed (elf) images cannot (apparently) be prelinked
> http://bugs.debian.org/262891
> http://bugs.debian.org/262890
>
> 2) Unexec'ed images on powerpc cannot be reliably stripped
> http://bugs.debian.org/210809
>
> Any ideas, or even just confirmations/refutations with emacs, most
> appreciated.

I'd expect emacs to have the same problems as described in the two bugs 
above, but I have not checked.  The trend seems to go to more 
complicated binary file formats, and more types of file formats.  This 
suggests to me that it might be a good time to rethink the whole unexec 
approach.  There must be some other more platform neutral way to save 
and restore state.

	Jan D.

  reply	other threads:[~2004-11-09  7:58 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.
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. [this message]
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=2D5E0BD2-3225-11D9-8E4D-000D93505B76@swipnet.se \
    --to=jan.h.d@swipnet.se \
    --cc=emacs-devel@gnu.org \
    --cc=gcl-devel@gnu.org \
    --cc=rms@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).