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 21:48:57 +0300 [thread overview]
Message-ID: <83edhhfcdi.fsf@gnu.org> (raw)
In-Reply-To: <m2msw5qkzy.fsf@Pro.fritz.box> (message from Gerd Möllmann on Thu, 26 Oct 2023 20:47:13 +0200)
> From: Gerd Möllmann <gerd.moellmann@gmail.com>
> Cc: Ihor Radchenko <yantar92@posteo.net>, 66744@debbugs.gnu.org
> Date: Thu, 26 Oct 2023 20:47:13 +0200
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > 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"?
>
> Please see my mail, which is more precise: it's always the same file F.
Then it shouldn't be. Each new dump should go to a new file, not to
the one we loaded in this session. There's no reason to try to debug
the crash, since TRT is just "not to do that".
next prev parent reply other threads:[~2023-10-26 18:48 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
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 [this message]
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
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=83edhhfcdi.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 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).