unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Gerd Möllmann" <gerd.moellmann@gmail.com>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: 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 17:45:49 +0200	[thread overview]
Message-ID: <m27cn9s7yq.fsf@Pro.fritz.box> (raw)
In-Reply-To: <87a5s5bg83.fsf@localhost> (Ihor Radchenko's message of "Thu, 26 Oct 2023 14:39:24 +0000")

Ihor Radchenko <yantar92@posteo.net> writes:

> Gerd Möllmann <gerd.moellmann@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.





  parent reply	other threads:[~2023-10-26 15:45 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 [this message]
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
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=m27cn9s7yq.fsf@Pro.fritz.box \
    --to=gerd.moellmann@gmail.com \
    --cc=66744@debbugs.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 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).