unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Po Lu <luangruo@yahoo.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: "Gerd Möllmann" <gerd.moellmann@gmail.com>,
	"Eli Zaretskii" <eliz@gnu.org>,
	rpluim@gmail.com, schwab@suse.de, emacs-devel@gnu.org
Subject: Re: Dumping unexec
Date: Sat, 20 Apr 2024 22:44:17 +0800	[thread overview]
Message-ID: <87zftogkla.fsf@yahoo.com> (raw)
In-Reply-To: <jwvmspoqhia.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Sat, 20 Apr 2024 09:43:32 -0400")

Stefan Monnier <monnier@iro.umontreal.ca> writes:

> IIUC, adding support for the pdumper to these systems should be fairly
> simple, consisting mostly of replacing calls to `mmap` with
> `malloc+read`.

Windows 9x's virtual memory facilities are adequate for the portable
dumper, but it crashes at runtime for reasons unknown with debugging a
vain endeavor.  DJGPP's fall short of what is required to implement
mprotect, under the memory extender they distribute, but there I've
never tried building the portable dump file loader already implemented
in pdumper.c.

> Has someone with access to such systems tried that?

Easier said than done: debugging Emacs on Windows 9x is a tedious
exercise that entails, among other tasks, transferring binaries between
the development machine and the target by way of an intermittent
connection to a Samba share, which is a hit or miss insofar as success
is concerned.  Not helping matters is the scarcity of time I can spend
with suitable target machines.

> Is there some more serious issue?

On my last attempt I failed to extract anything approaching an
intelligible backtrace from GDB.  However, none of these systems are to
receive support for the MPS, so why has it suddenly become an issue of
immediate importance that unexec be given the axe?



  parent reply	other threads:[~2024-04-20 14:44 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-18 15:01 Question about pure space Gerd Möllmann
2024-04-18 15:11 ` Andreas Schwab
2024-04-18 15:37   ` Gerd Möllmann
2024-04-19 15:48     ` Robert Pluim
2024-04-19 16:32       ` Gerd Möllmann
2024-04-19 16:49         ` Stefan Monnier
2024-04-19 17:38           ` Eli Zaretskii
2024-04-20  5:42             ` Gerd Möllmann
2024-04-20  6:17               ` Po Lu
2024-04-20 13:43                 ` Dumping unexec (was: Question about pure space) Stefan Monnier
2024-04-20 14:14                   ` Eli Zaretskii
2024-04-20 14:44                   ` Po Lu [this message]
2024-04-20 15:10                     ` Dumping unexec Gerd Möllmann
2024-04-20  6:25               ` Question about pure space Eli Zaretskii
2024-04-20  6:38                 ` Gerd Möllmann
2024-04-20 19:03                 ` Ulrich Mueller
2024-04-21  8:56                   ` James Le Cuirot
2024-04-20 23:31             ` Richard Stallman
2024-04-21  5:10               ` 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=87zftogkla.fsf@yahoo.com \
    --to=luangruo@yahoo.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=gerd.moellmann@gmail.com \
    --cc=monnier@iro.umontreal.ca \
    --cc=rpluim@gmail.com \
    --cc=schwab@suse.de \
    /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).