unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Po Lu <luangruo@yahoo.com>
Cc: emacs-devel@gnu.org
Subject: Re: Help with new Windows 98 crash
Date: Tue, 06 Dec 2022 16:32:13 +0200	[thread overview]
Message-ID: <83fsds7gcy.fsf@gnu.org> (raw)
In-Reply-To: <87r0xcn15q.fsf@yahoo.com> (message from Po Lu on Tue, 06 Dec 2022 20:53:53 +0800)

> From: Po Lu <luangruo@yahoo.com>
> Cc: emacs-devel@gnu.org
> Date: Tue, 06 Dec 2022 20:53:53 +0800
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> > There's nothing unsafe in what you did, but:
> >
> >   . the call to init_bignum inside the !initialized block should be
> >     conditioned on HAVE_UNEXEC
> 
> But doesn't it have to come before init_window_once in any case?
> Otherwise, the wrong malloc will be used even on pdumper builds.

You mean, in the pdumper build?  In that build, what init_bignum does is not
dumped, so I don't think we need it.  Otherwise, why didn't we see any
problems until now?

But if you want to call it in the pdumper build as well, I won't mind.  Just
let's make sure it is called only once upon each invocation.



  reply	other threads:[~2022-12-06 14:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87o7sindcl.fsf.ref@yahoo.com>
2022-12-05 14:18 ` Help with new Windows 98 crash Po Lu
2022-12-05 14:52   ` Eli Zaretskii
2022-12-05 16:59     ` Eli Zaretskii
2022-12-06  1:29       ` Po Lu
2022-12-06 12:12         ` Eli Zaretskii
2022-12-06 12:53           ` Po Lu
2022-12-06 14:32             ` Eli Zaretskii [this message]
2022-12-07  0:59               ` Po Lu

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=83fsds7gcy.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@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).