From: Eli Zaretskii <eliz@gnu.org>
To: "Kévin Le Gouguec" <kevin.legouguec@gmail.com>,
"Daniel Colascione" <dancol@dancol.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 10:12:44 +0200 [thread overview]
Message-ID: <83blslhnyb.fsf@gnu.org> (raw)
In-Reply-To: <87o8wnj4nf.fsf@gmail.com> (message from Kévin Le Gouguec on Wed, 04 Dec 2019 20:02:12 +0100)
> From: Kévin Le Gouguec <kevin.legouguec@gmail.com>
> Date: Wed, 04 Dec 2019 20:02:12 +0100
>
> For some reason, one of my setups[1] experiences a pure storage overflow
> with the current master[2]. Searching previous bug reports for the
> warning[3] led me to understand that increasing BASE_PURESIZE in
> src/puresize.h would solve the issue; since I didn't have the patience
> to recompile possibly multiple times, I tried to find a way to know
> exactly how much I should increase this value.
>
> I noticed that Fdump_emacs uses check_pure_size from alloc.c to print a
> warning before dumping when this happens. The following patch exposes
> check_pure_size when we HAVE_PDUMPER, so that Fdump_emacs_portable can
> use it too.
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.
Daniel, what are your thoughts about this?
next prev parent reply other threads:[~2019-12-06 8:12 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 [this message]
2019-12-06 16:37 ` Kévin Le Gouguec
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83blslhnyb.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=38492@debbugs.gnu.org \
--cc=dancol@dancol.org \
--cc=kevin.legouguec@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.