From: Paul Eggert <eggert@cs.ucla.edu>
To: Eli Zaretskii <eliz@gnu.org>
Cc: p.stephani2@gmail.com, philippe.vaucher@gmail.com, 23529@debbugs.gnu.org
Subject: bug#23529: Request for fixing randomize_va_space build issues
Date: Tue, 6 Sep 2016 13:37:20 -0700 [thread overview]
Message-ID: <d52cfb32-0143-95c2-8bff-d097f0b8a2e8@cs.ucla.edu> (raw)
In-Reply-To: <83twdsalbk.fsf@gnu.org>
On 09/06/2016 12:18 PM, Eli Zaretskii wrote:
> Then users on those platforms will never be able to re-dump.
True. But they'll still be better off than they are now, since they
can't dump at all now. Plus, for extra credit we could dynamically link
the dumped object modules at Emacs startup, with the idea of making it
practical to re-dump.
> I actually don't understand why the data should be serialized as C
> code. Why not just data that is read into memory (with conversion to
> the native format)? A compiler is not the only way to convert text
> into binary data.
The compiler-based approach should be simpler and more portable than
messing with low-level binary I/O. For example, it should be easy to
arrange for some of the objects to be read-only: just declare them to be
'const'. Another example: on hardened platforms with PIEs
(position-independent executables), you get a PIE for free as the dumped
executable, instead of having to disable PIE as we do now.
Although Emacs can do this sort of work itself (e.g., randomizing
locations of dumped objects, munging pointers as they come in to match
the random locations, and using mmap to make the relevant objects
const), it should be better for Emacs to use the linking technology
already available on modern platforms, rather than trying to reinvent
the wheel.
next prev parent reply other threads:[~2016-09-06 20:37 UTC|newest]
Thread overview: 66+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-13 12:18 bug#23529: Request for fixing randomize_va_space build issues Philippe Vaucher
2016-05-13 15:58 ` Paul Eggert
2016-05-17 16:38 ` Philippe Vaucher
2016-05-18 7:53 ` Philippe Vaucher
2016-05-18 8:21 ` Paul Eggert
2016-05-18 8:44 ` Philippe Vaucher
2016-05-20 17:52 ` Paul Eggert
2016-09-06 9:22 ` Philipp Stephani
2016-09-06 17:21 ` Paul Eggert
2016-09-06 17:40 ` Eli Zaretskii
2016-09-06 17:46 ` Philippe Vaucher
2016-09-06 17:55 ` Philipp Stephani
2016-09-06 18:04 ` Eli Zaretskii
2016-09-06 17:59 ` Eli Zaretskii
2016-09-06 18:03 ` Philipp Stephani
2016-09-06 18:32 ` Eli Zaretskii
2016-09-06 19:01 ` Philipp Stephani
2016-09-06 18:24 ` Philippe Vaucher
2016-09-06 19:11 ` Eli Zaretskii
2016-09-06 18:18 ` Clément Pit--Claudel
2016-09-06 19:09 ` Eli Zaretskii
2016-09-06 19:59 ` Clément Pit--Claudel
2016-09-06 18:44 ` Paul Eggert
2016-09-06 19:18 ` Eli Zaretskii
2016-09-06 20:37 ` Paul Eggert [this message]
2016-09-07 7:12 ` Philippe Vaucher
2016-09-07 7:40 ` Paul Eggert
2016-09-07 11:01 ` Philipp Stephani
2016-09-07 14:21 ` Eli Zaretskii
2016-09-07 16:11 ` Paul Eggert
2016-09-07 17:10 ` Eli Zaretskii
2016-09-07 17:40 ` Paul Eggert
2016-09-07 18:11 ` Eli Zaretskii
2016-09-07 20:12 ` Paul Eggert
2016-09-09 5:40 ` Eli Zaretskii
2016-09-09 7:10 ` Paul Eggert
2016-09-09 7:50 ` Eli Zaretskii
2016-09-09 8:54 ` Paul Eggert
2016-09-09 9:09 ` Eli Zaretskii
2016-09-09 16:16 ` Paul Eggert
2016-09-09 18:45 ` Eli Zaretskii
2016-09-09 19:59 ` Paul Eggert
2016-09-10 6:06 ` Eli Zaretskii
2016-09-10 7:52 ` Paul Eggert
2016-09-10 10:19 ` Eli Zaretskii
2016-09-10 23:01 ` Paul Eggert
2016-09-11 15:23 ` Eli Zaretskii
2016-09-11 16:59 ` Paul Eggert
2016-09-11 17:19 ` Eli Zaretskii
2016-09-11 19:32 ` Philippe Vaucher
2016-09-12 2:30 ` Eli Zaretskii
2016-09-12 2:58 ` Clément Pit--Claudel
2016-09-12 6:09 ` Philipp Stephani
2016-09-12 17:04 ` Eli Zaretskii
2016-09-12 14:10 ` Philippe Vaucher
2016-09-12 14:18 ` Philippe Vaucher
2016-09-13 14:47 ` Eli Zaretskii
2016-09-13 15:21 ` Philippe Vaucher
2016-09-13 15:55 ` Eli Zaretskii
2016-09-13 15:51 ` Paul Eggert
2016-09-13 19:24 ` Eli Zaretskii
2016-09-09 20:00 ` Philippe Vaucher
2016-09-10 6:13 ` Eli Zaretskii
2016-09-09 18:29 ` Andreas Schwab
2016-09-09 18:56 ` Eli Zaretskii
-- strict thread matches above, loose matches on Subject: below --
2019-09-14 4:18 bug#13964: " Stefan Kangas
2019-09-14 8:52 ` Philippe Vaucher
2019-09-14 10:39 ` Stefan Kangas
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=d52cfb32-0143-95c2-8bff-d097f0b8a2e8@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=23529@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=p.stephani2@gmail.com \
--cc=philippe.vaucher@gmail.com \
/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).