From: Eli Zaretskii <eliz@gnu.org>
To: Nikolay Kudryavtsev <nikolay.kudryavtsev@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Unexec dumping results in "Segmentation fault" on Windows Msys2
Date: Fri, 30 Apr 2021 14:24:53 +0300 [thread overview]
Message-ID: <834kfoc8vu.fsf@gnu.org> (raw)
In-Reply-To: <e069fbec-d82f-69d8-f8fa-e788dd05e86e@gmail.com> (message from Nikolay Kudryavtsev on Thu, 29 Apr 2021 22:17:10 +0300)
> From: Nikolay Kudryavtsev <nikolay.kudryavtsev@gmail.com>
> Cc: emacs-devel@gnu.org
> Date: Thu, 29 Apr 2021 22:17:10 +0300
>
> I now know what's going on there.
>
> buffer.c/init_buffer has some unexec-specific code that remaps memory
> for the special buffers inherited from temacs. We fail at
> Fprin1_to_string which uses the " prin1" special buffer. cddf85d256
> removed FOR_EACH_BUFFER macro and replaced it everywhere with the use of
> FOR_EACH_LIVE_BUFFER. Because FOR_EACH_LIVE_BUFFER does not iterate over
> the " prin1" buffer, it does not get its memory remapped and this breaks
> print functionality and elisp compilation, which depends on it.
>
> FOR_EACH_BUFFER worked before due to buffer structure operating as a
> linked list and since it's kind of an ugly way of doing things, make
> sense why Stefan removed it. But I'm not if adding those special buffers
> to Vbuffer_alist(FOR_EACH_LIVE_BUFFER uses it) would not break anything.
Thanks. The " prin1" buffer is not in Vbuffer_alist intentionally. I
installed a possible fix for this on master (100% untested), please
see if it fixes the problem.
next prev parent reply other threads:[~2021-04-30 11:24 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-03 20:20 Unexec dumping results in "Segmentation fault" on Windows Msys2 Nikolay Kudryavtsev
2021-04-04 7:11 ` Eli Zaretskii
2021-04-04 7:55 ` Eli Zaretskii
2021-04-04 8:41 ` Nikolay Kudryavtsev
2021-04-04 11:34 ` Eli Zaretskii
2021-04-14 22:11 ` Nikolay Kudryavtsev
2021-04-15 6:49 ` Eli Zaretskii
2021-04-15 13:07 ` Camm Maguire
2021-04-15 13:49 ` Eli Zaretskii
2021-04-15 15:47 ` Nikolay Kudryavtsev
2021-04-15 16:08 ` Eli Zaretskii
2021-04-15 19:17 ` Nikolay Kudryavtsev
2021-04-15 19:59 ` Eli Zaretskii
2021-04-16 16:57 ` Nikolay Kudryavtsev
2021-04-16 19:41 ` Eli Zaretskii
2021-04-21 16:33 ` Nikolay Kudryavtsev
2021-04-21 17:41 ` Eli Zaretskii
2021-04-21 18:19 ` Nikolay Kudryavtsev
2021-04-22 14:25 ` Eli Zaretskii
2021-04-29 19:17 ` Nikolay Kudryavtsev
2021-04-30 11:24 ` Eli Zaretskii [this message]
2021-05-02 9:43 ` Nikolay Kudryavtsev
2021-05-02 10:17 ` Eli Zaretskii
2021-04-22 17:22 ` Eli Zaretskii
2021-04-22 18:59 ` Nikolay Kudryavtsev
2021-04-22 19:13 ` Eli Zaretskii
2021-04-22 19:26 ` Nikolay Kudryavtsev
2021-04-16 7:45 ` Eli Zaretskii
2021-04-15 16:12 ` Eli Zaretskii
2021-04-15 19:45 ` Nikolay Kudryavtsev
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=834kfoc8vu.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=nikolay.kudryavtsev@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).