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: Sun, 11 Sep 2016 09:59:52 -0700 [thread overview]
Message-ID: <2112c911-8613-01fd-2ec5-dfc29002acce@cs.ucla.edu> (raw)
In-Reply-To: <83fup6bguo.fsf@gnu.org>
Eli Zaretskii wrote:
> What do you mean by
> "relocating objects", and why would we need to do that as part of
> un-dumping?
Objects in the new Emacs might have different addresses from objects in the old
Emacs, due to address randomization.
>> What about disabling randomization for the temacs run?
>>
>> That is yet another low-level thing to configure, and to get right in new ports.
>
> We already have that in Emacs, don't we?
Yes, and that's one of the problems that we should fix. It causes us to run into
portability problems. It's still not clear that the current implementation will
actually work on POSIXish systems. We are on (or over) the edge of portability
here, and we need to get off.
> No, this point started with me saying dumping and reading dumped data
> with fixups is relatively easy, and you objecting saying address
> randomizations will defeat that. Now we agree that it's a tangential
> issue unrelated to my proposal.
We don't agree.
next prev parent reply other threads:[~2016-09-11 16:59 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2112c911-8613-01fd-2ec5-dfc29002acce@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.