all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Pip Cet <pipcet@gmail.com>
To: 46965@debbugs.gnu.org
Subject: bug#46965: 28.0.50; unexec does not build (or work)
Date: Sat, 6 Mar 2021 14:01:44 +0000	[thread overview]
Message-ID: <CAOqdjBcqA84=AUPfnqV-Am78N4R87FUuAD26rP3HXbUa3d-iRA@mail.gmail.com> (raw)

On this Debian-based x86_64-pc-linux-gnu system, configuring with
--with-dumping=unexec results in various errors:

1. a compilation error in pdumper.c. Easy to fix, my fault, but then there's ...
2. a segfault when running the dumped image. The problem is we can't
use glibc's malloc when running a dumped image, so we need to force
use of hybrid malloc. But then...
3. gnulib no longer builds with hybrid malloc. To do so requires some
massaging of the gnulib files, but then...
4. gnulib redirects free() to always point to the glibc free(), even
when Emacs wants to override it for hybrid malloc. To fix this, we
need to rerun gnulib-tool.

(1) tells me it's very unlikely anyone but me has tried to build
unexec Emacs lately. The other bugs tell me that it's getting rapidly
more difficult to support unexec build.

But unexec does provide performance advantages over pdumper, and even
over undumped builds.

So, do we want to keep it as an option? RMS said so in

https://debbugs.gnu.org/cgi/bugreport.cgi?bug=36649;msg=77

So I'm opening this bug for discussion, and to post the patches I need
to make unexec work again.





             reply	other threads:[~2021-03-06 14:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-06 14:01 Pip Cet [this message]
2021-03-06 19:07 ` bug#46965: 28.0.50; unexec does not build (or work) Pip Cet
2021-03-06 20:04   ` Eli Zaretskii
2021-03-06 20:19     ` Pip Cet
2022-06-20  1:27 ` Lars Ingebrigtsen

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='CAOqdjBcqA84=AUPfnqV-Am78N4R87FUuAD26rP3HXbUa3d-iRA@mail.gmail.com' \
    --to=pipcet@gmail.com \
    --cc=46965@debbugs.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 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.