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

Package: emacs;

Reported by: Ihor Radchenko <yantar92 <at> posteo.net>

Date: Wed, 25 Oct 2023 10:01:02 UTC

Severity: normal

Tags: notabug, wontfix

Found in version 30.0.50

Fixed in version 30.1

Done: Gerd Möllmann <gerd.moellmann <at> gmail.com>

Bug is archived. No further changes may be made.

Full log


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

From: Gerd Möllmann <gerd.moellmann <at> gmail.com>
To: Ihor Radchenko <yantar92 <at> posteo.net>
Cc: 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 17:45:49 +0200
Ihor Radchenko <yantar92 <at> posteo.net> writes:

> Gerd Möllmann <gerd.moellmann <at> gmail.com> writes:
>
>>> 2. ./src/emacs -Q --dump-file="/tmp/emacs-dumped.dmp"
>>
>> I wasn't yet able to reproduce this here, on macOS.
>>
>> The stack trace says it's during mouse-highlighting, so chances are it's
>> not related to the dump in step 3. What happens when you leave out step
>> 3, and just try some mouse-highligting in the Emacs from step 2?
>
> I am running Emacs from step 2 for more than 24 hours by now with normal
> usage.

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 :-).

I'll leave it to the maintainers to decide if this needs action.




This bug report was last modified 1 year and 206 days ago.

Previous Next


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