GNU bug report logs - #36649
27.0.50; pure space and pdumper

Previous Next

Full log

View this message in rfc822 format

From: Lars Ingebrigtsen <larsi <at> gnus.org>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: eggert <at> cs.ucla.edu, rpluim <at> gmail.com, stefan <at> marxist.se, schwab <at> linux-m68k.org, monnier <at> iro.umontreal.ca, pipcet <at> gmail.com, 36649 <at> debbugs.gnu.org, akrl <at> sdf.org
Subject: bug#36649: 27.0.50; pure space and pdumper
Date: Sun, 16 May 2021 15:38:26 +0200

Eli Zaretskii <eliz <at> gnu.org> writes:

> Looks like some memory problem: xrealloc segfaults.
>
> Don't we need to disable ASLR for unexec to work?  And doesn't that
> require setfattr or paxctl commands to be available?  If not, how do
> we disable ASLR in bootstrap-emacs and emacs binaries on GNU/Linux?

Hm...  the PROBLEMS file has this:

----
These segfaults should not occur on most modern systems, because the
Emacs build procedure uses the command 'setfattr' or 'paxctl' to mark
the Emacs executable as requiring non-randomized address space, and
Emacs uses the 'personality' system call to disable address space
randomization when dumping.
----

Is that correct?  I thought we had ASLR switched on on GNU/Linux builds?

----
To work around the ASLR problem in either an older or a newer kernel,
you can temporarily disable the feature while building Emacs.  On
GNU/Linux you can do so using the following command (as root).

    echo 0 > /proc/sys/kernel/randomize_va_space
----

I tried this recipe now on Debian/bullseye, but the unexec build still
segfaults.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.