From: Daniel Colascione <dancol@dancol.org>
To: "Gerd Möllmann" <gerd.moellmann@gmail.com>,
"Lars Ingebrigtsen" <larsi@gnus.org>
Cc: Po Lu <luangruo@yahoo.com>, Eli Zaretskii <eliz@gnu.org>,
50453@debbugs.gnu.org
Subject: bug#50453: 27.2; Portable dumper broken on MSW
Date: Thu, 25 Aug 2022 19:37:20 -0700 [thread overview]
Message-ID: <182d802d300.2829.cc5b3318d7e9908e2c46732289705cb0@dancol.org> (raw)
In-Reply-To: <m2czcoe5xw.fsf@Mini.fritz.box>
[-- Attachment #1: Type: text/plain, Size: 627 bytes --]
On August 25, 2022 07:47:12 Gerd Möllmann <gerd.moellmann@gmail.com> wrote:
> Lars Ingebrigtsen <larsi@gnus.org> writes:
>
>>> And while at that, can you tell why we request
>>> DUMP_MEMORY_ACCESS_READWRITE and not DUMP_MEMORY_ACCESS_READ when
>>> loading from the pdumper file? Do we expect the need to change values
>>> loaded from the file?
>>
>> This is still the case on the trunk. Daniel, do you have any comments
>> here?
>
> I'm not Daniel, but what about relocations? After mapping a .pdmp,
> pointers have to be computed that fit the location in memory where the
> .pdmp has been mapped.
Right. We want COW.
[-- Attachment #2: Type: text/html, Size: 1745 bytes --]
next prev parent reply other threads:[~2022-08-26 2:37 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <871r60v9i0.fsf.ref@yahoo.com>
2021-09-07 12:46 ` bug#50453: 27.2; Portable dumper broken on MSW Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-09-07 13:47 ` Eli Zaretskii
2021-09-08 12:37 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-09-08 13:25 ` Eli Zaretskii
2021-09-09 8:07 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-09-09 11:34 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-09-09 11:57 ` Eli Zaretskii
2021-09-09 12:40 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-09-09 12:55 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-09-09 16:28 ` Eli Zaretskii
2021-09-10 0:48 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-09-10 12:18 ` Eli Zaretskii
2021-09-11 2:57 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-09-11 6:47 ` Eli Zaretskii
2022-08-25 14:24 ` Lars Ingebrigtsen
2022-08-25 14:47 ` Gerd Möllmann
2022-08-26 2:37 ` Daniel Colascione [this message]
2022-08-26 10:43 ` Lars Ingebrigtsen
2022-08-26 1:05 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-26 6:00 ` Eli Zaretskii
2022-08-26 7:40 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-26 10:39 ` Eli Zaretskii
2021-09-09 16:24 ` Eli Zaretskii
2021-09-10 0:51 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-09-09 11:58 ` Eli Zaretskii
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=182d802d300.2829.cc5b3318d7e9908e2c46732289705cb0@dancol.org \
--to=dancol@dancol.org \
--cc=50453@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=gerd.moellmann@gmail.com \
--cc=larsi@gnus.org \
--cc=luangruo@yahoo.com \
/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).