From: Eli Zaretskii <eliz@gnu.org>
To: Po Lu <luangruo@yahoo.com>
Cc: stefankangas@gmail.com, pipcet@protonmail.com, emacs-devel@gnu.org
Subject: Re: Pure space
Date: Sat, 17 Aug 2024 17:12:40 +0300 [thread overview]
Message-ID: <86wmkf1bmv.fsf@gnu.org> (raw)
In-Reply-To: <87y14vi849.fsf@yahoo.com> (message from Po Lu on Sat, 17 Aug 2024 21:36:38 +0800)
> From: Po Lu <luangruo@yahoo.com>
> Cc: Stefan Kangas <stefankangas@gmail.com>, pipcet@protonmail.com,
> emacs-devel@gnu.org
> Date: Sat, 17 Aug 2024 21:36:38 +0800
>
> >> > Portable dumping doesn't function on Windows 98 or DOS. Please fix or
> >> > implement pdumper on these two platforms first, or hack their unexec
> >> > builds not to require pure space, which should not be terribly
> >> > difficult.
> >>
> >> In my view, that's not a blocker for removing the unexec build.
> >
> > Agreed.
>
> The Windows 98 build is: it has many users and it is in a satisfactory
> condition at present, so it would be a terrible regression.
Then the interested users and developers should come forward and help
us find and fix whatever causes the crashes. I have not seen any such
users, with you being the single exception, for a long time. If you
can get someone motivated to work with us on fixing pdumper.c on
Windows 9X, please do, and let's take it from there. Such an effort
will at least be an investment in the future.
> It crashes 100% of the time, actually, not merely "too much", which I
> can't investigate without a functioning gdb, and which is very much
> against the spirit of the word "portable". Unless one of you are
> willing to show me a GDB that is newer than Code::Blocks provides and
> which groks recent DWARF debug info, I don't forsee any solution.
There's such a thing as printf debugging. It is far from ideal, but
it's doable.
> > If we want to keep the MSDOS port, the way forward is to switch it to
> > pdumper. There's already an implementation in pdumper.c that uses
> > malloc and write instead of the missing mmap, it just was never tried
> > with the MSDOS port. I don't see any reasons why it couldn't work.
>
> Why can't unexecoff be retained without pure space?
Because Emacs never used this combination, and because no one has time
or knowhow to debug the MSDOS port anymore (which still uses COFF
debug info, which makes the job of finding a proper GDB even harder).
I might be the last person who can do that, and I don't have time to
do that seriously, when significant problems pop up.
> There's also no reason against this enormously simpler solution
It is simple source code wise, but it is not a solution, it is a
problem. We never used Emacs that way, and I'm quite sure this will
trigger strange bugs that I don't want us to need to debug.
Keeping the MSDOS build alive means keeping it in good health. While
the current code base has some significant number of years under its
belt (although that, too, becomes smaller and smaller as years go by
and more significant code changes are installed) the version without
pure space was never used before.
next prev parent reply other threads:[~2024-08-17 14:12 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-16 19:07 Pure space Pip Cet
2024-08-17 6:18 ` Eli Zaretskii
2024-08-17 6:59 ` Stefan Kangas
2024-08-17 8:14 ` Po Lu
2024-08-17 12:10 ` Stefan Kangas
2024-08-17 12:53 ` Eli Zaretskii
2024-08-17 13:36 ` Po Lu
2024-08-17 14:12 ` Eli Zaretskii [this message]
2024-08-17 8:45 ` Pip Cet
2024-08-17 10:51 ` Eli Zaretskii
2024-08-17 11:38 ` Pip Cet
2024-08-17 13:13 ` Eli Zaretskii
2024-08-17 13:26 ` Pip Cet
2024-08-17 14:29 ` Eli Zaretskii
2024-08-17 14:35 ` Pip Cet
2024-08-17 13:11 ` Stefan Kangas
2024-08-17 14:30 ` Pip Cet
2024-08-17 15:34 ` Andrea Corallo
2024-08-17 15:41 ` Pip Cet
2024-08-17 8:16 ` Po Lu
2024-08-17 8:28 ` Po Lu
2024-08-17 8:31 ` Po Lu
2024-08-17 8:57 ` Pip Cet
2024-08-17 11:06 ` Eli Zaretskii
2024-08-17 10:45 ` Eli Zaretskii
2024-08-17 11:46 ` Po Lu
2024-08-17 12:49 ` Eli Zaretskii
2024-08-17 13:44 ` Po Lu
2024-08-17 14:17 ` 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=86wmkf1bmv.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=luangruo@yahoo.com \
--cc=pipcet@protonmail.com \
--cc=stefankangas@gmail.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).