From: Ken Raeburn <raeburn@raeburn.org>
Date: Wed, 5 Apr 2017 06:48:49 +0000 (-0400)
Subject: In CANNOT_DUMP builds, don't prepare for unexec.
X-Git-Tag: emacs-26.0.90~521^2~708
X-Git-Url: http://git.eshelyaron.com/gitweb/?a=commitdiff_plain;h=8ca2bd1ce7eebaf3b995786d9f9f61907ebbb060;p=emacs.git

In CANNOT_DUMP builds, don't prepare for unexec.

Having a command-line argument of "dump" or "bootstrap" would trigger
behavior like not installing signal handlers.  In CANNOT_DUMP modes,
we should get signal handlers installed regardless of whatever funny
file names we decide to edit.

src/emacs.c (main) [CANNOT_DUMP]: Don't enable the "dumping"
alterations to initialization that prepares the process for unexec.
---

diff --git a/src/emacs.c b/src/emacs.c
index 2b01a37f5ab..9339d60866c 100644
--- a/src/emacs.c
+++ b/src/emacs.c
@@ -683,8 +683,12 @@ main (int argc, char **argv)
   /* Record (approximately) where the stack begins.  */
   stack_bottom = &stack_bottom_variable;
 
+#ifndef CANNOT_DUMP
   dumping = !initialized && (strcmp (argv[argc - 1], "dump") == 0
 			     || strcmp (argv[argc - 1], "bootstrap") == 0);
+#else
+  dumping = false;
+#endif
 
   /* True if address randomization interferes with memory allocation.  */
 # ifdef __PPC64__