From: "Gerd Möllmann" <gerd.moellmann@gmail.com>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: Eli Zaretskii <eliz@gnu.org>, 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 20:42:29 +0200 [thread overview]
Message-ID: <m2r0lhql7u.fsf@Pro.fritz.box> (raw)
In-Reply-To: <874jidb5cf.fsf@localhost> (Ihor Radchenko's message of "Thu, 26 Oct 2023 18:34:24 +0000")
Ihor Radchenko <yantar92@posteo.net> writes:
> Eli Zaretskii <eliz@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.
Ihor, maybe you could run emacs in a debuuger with a breakpoint on dump_map_file, so that we know
for sure if mmap is called?
gdb emacs
(gdb) b dump_map_file
(gbd) r -Q --dump-file <file> # or what the command line was...
next prev parent reply other threads:[~2023-10-26 18:42 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
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 [this message]
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=m2r0lhql7u.fsf@Pro.fritz.box \
--to=gerd.moellmann@gmail.com \
--cc=66744@debbugs.gnu.org \
--cc=eliz@gnu.org \
--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.