From: Lars Ingebrigtsen <larsi@gnus.org>
To: Pip Cet <pipcet@gmail.com>
Cc: 46965@debbugs.gnu.org
Subject: bug#46965: 28.0.50; unexec does not build (or work)
Date: Mon, 20 Jun 2022 03:27:02 +0200 [thread overview]
Message-ID: <87a6a8qg49.fsf@gnus.org> (raw)
In-Reply-To: <CAOqdjBcqA84=AUPfnqV-Am78N4R87FUuAD26rP3HXbUa3d-iRA@mail.gmail.com> (Pip Cet's message of "Sat, 6 Mar 2021 14:01:44 +0000")
Pip Cet <pipcet@gmail.com> writes:
> 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...
(I'm going through old bug reports that unfortunately weren't resolved
at the time.)
It looks like this was fixed in:
commit 44ed8f6555288f00b982f21e68ac5a51372279de
Author: Eli Zaretskii <eliz@gnu.org>
AuthorDate: Sun Apr 4 10:10:00 2021 +0300
And the unexec build seems to work OK for me still, so I'm closing this
bug report. (If there's more to be done here, please respond to the
debbugs address and we'll reopen.)
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
prev parent reply other threads:[~2022-06-20 1:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-06 14:01 bug#46965: 28.0.50; unexec does not build (or work) Pip Cet
2021-03-06 19:07 ` Pip Cet
2021-03-06 20:04 ` Eli Zaretskii
2021-03-06 20:19 ` Pip Cet
2022-06-20 1:27 ` Lars Ingebrigtsen [this message]
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=87a6a8qg49.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=46965@debbugs.gnu.org \
--cc=pipcet@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).