GNU bug report logs - #66744
30.0.50; Emacs crashes when re-dumping into the same dump file another Emacs instance is using

Previous Next

Full log

Message #26 received at 66744 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Gerd Möllmann <gerd.moellmann <at> gmail.com>
Cc: yantar92 <at> posteo.net, 66744 <at> debbugs.gnu.org
Subject: Re: 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 21:18:25 +0300

> From: Gerd Möllmann <gerd.moellmann <at> gmail.com>
> Cc: yantar92 <at> posteo.net,  66744 <at> debbugs.gnu.org
> Date: Thu, 26 Oct 2023 18:32:23 +0200
> 
> Eli Zaretskii <eliz <at> gnu.org> writes:
> 
> >> Cc: 66744 <at> debbugs.gnu.org
> >> From: Gerd Möllmann <gerd.moellmann <at> 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.
> 
> Ok, but I must admit that I don't see how that is done in pdumper.c.

Then maybe I don't understand what bothers you.  What are the "changes
made to the dump file in step 3" to which you allude?  AFRAIU, step 3
simply loads the dump file, it doesn't change the file.  What did I
miss?

Previous Next

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