unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 50453@debbugs.gnu.org
Subject: bug#50453: 27.2; Portable dumper broken on MSW
Date: Wed, 08 Sep 2021 20:37:34 +0800	[thread overview]
Message-ID: <87y287nsz5.fsf@yahoo.com> (raw)
In-Reply-To: <83eea0pkdz.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 07 Sep 2021 16:47:52 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

> How do you mean "operates normally if the portable dump file is
> removed"?  Without a pdmp file, Emacs should load all the preloaded
> Lisp files when it starts up, which is definitely not something I'd
> call "normal".  Don't you see a long series of "Loading foo..."
> messages when Emacs starts without a pdmp file?

I meant to say that while Emacs does load loadup.el from source, it more
or less works normally after the load completes.

> First, the important figure is how much of the 768MB is free when
> Emacs loads.

That shouldn't be a problem; none of the indicators in the resource
meter report more than 45% utilization when the crash occurs.

> And second, you are using Emacs on Windows 9X, something that a few
> people do, so perhaps we have some bug related to that version of
> Windows.  If you can run Emacs under GDB, please step through
> pdumper_load and tell where it bails out.

That is proving to be a problem.  MinGW flat out refuses to start, while
the GDB from ezwinports complains about "KERNEL32.DLL" missing the
symbol "AttachConsole".  Do you know how I can obtain a copy of GDB that
will still work on this old system?  Thanks in advance!





  reply	other threads:[~2021-09-08 12: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 [this message]
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
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=87y287nsz5.fsf@yahoo.com \
    --to=bug-gnu-emacs@gnu.org \
    --cc=50453@debbugs.gnu.org \
    --cc=eliz@gnu.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).