unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Kévin Le Gouguec" <kevin.legouguec@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 38492@debbugs.gnu.org
Subject: bug#38492: 27.0.50; Warn pdumper users when pure space has been overflowed
Date: Fri, 06 Dec 2019 17:37:49 +0100	[thread overview]
Message-ID: <87muc5wgte.fsf@gmail.com> (raw)
In-Reply-To: <83blslhnyb.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 06 Dec 2019 10:12:44 +0200")

Eli Zaretskii <eliz@gnu.org> writes:

> I'm not sure we should care about overflowing the pure space in
> pdumped Emacs.  Why does it matter?  It mattered in unexec'ed Emacs,
> that's why we warned about it.  Maybe the right solution is to remove
> the warning from startup.el instead.

Sorry for the false alarm then.  I took the startup warning at face
value; I didn't see anything in (elisp)Pure Storage suggesting that the
portable dumper invalidated it.

Had I tried to run garbage-collect manually, I would have noticed that
the return value was non-nil, suggesting that GC wasn't disabled…





  reply	other threads:[~2019-12-06 16:37 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-04 19:02 bug#38492: 27.0.50; Warn pdumper users when pure space has been overflowed Kévin Le Gouguec
2019-12-06  8:12 ` Eli Zaretskii
2019-12-06 16:37   ` Kévin Le Gouguec [this message]
2019-12-06 16:49     ` Daniel Colascione
2019-12-06 18:51       ` Eli Zaretskii
2019-12-06 19:02         ` dancol
2019-12-07  4:48           ` Richard Stallman
2019-12-07  7:59             ` Eli Zaretskii
2019-12-15 20:41             ` Stefan Monnier
2019-12-15 20:45               ` Daniel Colascione
2019-12-17  3:09               ` Richard Stallman
2019-12-14 11:42           ` Eli Zaretskii
2019-12-14 14:09             ` Kévin Le Gouguec
2019-12-15 20:33           ` Stefan Monnier
2019-12-15 20:41             ` Daniel Colascione
2019-12-17  3:09             ` Richard Stallman

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=87muc5wgte.fsf@gmail.com \
    --to=kevin.legouguec@gmail.com \
    --cc=38492@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    /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).