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 #32 received at 66744 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Ihor Radchenko <yantar92 <at> posteo.net>
Cc: gerd.moellmann <at> gmail.com, 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:41:42 +0300
> From: Ihor Radchenko <yantar92 <at> posteo.net>
> Cc: Gerd Möllmann <gerd.moellmann <at> gmail.com>,
>  66744 <at> debbugs.gnu.org
> Date: Thu, 26 Oct 2023 18:34:24 +0000
> 
> Eli Zaretskii <eliz <at> gnu.org> writes:
> 
> > 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?
> 
> step 1: create the dump file
> step 2: load Emacs with the created dump file
> step 3: repeat step 1 while Emacs is running -> running Emacs crashes
>      once I interact with its frame.
> 
> Hope it is more clear.

Thanks, but no, it isn't.  Step 3 writes a new and different dump
file, doesn't it?  So how could those changes be "visible in the
mmaped dump file that Emacs from step 2 uses"?




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

Previous Next


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