From: Eli Zaretskii <eliz@gnu.org>
To: "Gerd Möllmann" <gerd.moellmann@gmail.com>
Cc: yantar92@posteo.net, 66744@debbugs.gnu.org
Subject: bug#66744: 30.0.50; Emacs crashes when re-dumping into the same dump file another Emacs instance is using
Date: Thu, 26 Oct 2023 18:58:34 +0300 [thread overview]
Message-ID: <83msw5fk9h.fsf@gnu.org> (raw)
In-Reply-To: <m27cn9s7yq.fsf@Pro.fritz.box> (message from Gerd Möllmann on Thu, 26 Oct 2023 17:45:49 +0200)
> Cc: 66744@debbugs.gnu.org
> From: Gerd Möllmann <gerd.moellmann@gmail.com>
> Date: Thu, 26 Oct 2023 17:45:49 +0200
>
> The linux man page for mmap says, according to Google,
>
> MAP_PRIVATE
> ...
> It is unspecified whether changes made to the file
> after the mmap() call are visible in the mapped region.
>
> So, if the changes made to the dump file in step 3 are visible in the
> mmaped dump file that Emacs from step 2 uses, that would be a bit
> suboptimal :-).
Emacs on GNU/Linux doesn't use mmap, we stopped doing this many years
ago.
It could be relevant to MS-Windows, which emulates mmap and uses the
relevant code in Emacs. But Ihor doesn't use MS-Windows, AFAIK.
next prev parent reply other threads:[~2023-10-26 15:58 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-25 10:01 bug#66744: 30.0.50; Emacs crashes when re-dumping into the same dump file another Emacs instance is using Ihor Radchenko
2023-10-26 14:10 ` Gerd Möllmann
2023-10-26 14:39 ` Ihor Radchenko
2023-10-26 14:42 ` Gerd Möllmann
2023-10-26 15:45 ` Gerd Möllmann
2023-10-26 15:58 ` Eli Zaretskii [this message]
2023-10-26 16:32 ` Gerd Möllmann
2023-10-26 18:18 ` Eli Zaretskii
2023-10-26 18:26 ` Gerd Möllmann
2023-10-26 18:34 ` Ihor Radchenko
2023-10-26 18:41 ` Eli Zaretskii
2023-10-26 18:47 ` Gerd Möllmann
2023-10-26 18:48 ` Eli Zaretskii
2023-10-26 19:03 ` Ihor Radchenko
2023-10-26 19:23 ` Gerd Möllmann
2023-10-27 5:33 ` Eli Zaretskii
2023-10-26 18:42 ` Gerd Möllmann
2023-10-26 19:28 ` Andreas Schwab
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=83msw5fk9h.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=66744@debbugs.gnu.org \
--cc=gerd.moellmann@gmail.com \
--cc=yantar92@posteo.net \
/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.