unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Luc Teirlinck <teirllm@dms.auburn.edu>
Cc: emacs-devel@gnu.org, handa@m17n.org
Subject: Re: dump-emacs doesn't fail even if Pure Lisp storage overflows
Date: Sat, 21 Jan 2006 20:15:41 -0600 (CST)	[thread overview]
Message-ID: <200601220215.k0M2Ffs02046@raven.dms.auburn.edu> (raw)
In-Reply-To: <87slrhedhb.fsf@jurta.org> (message from Juri Linkov on Sun, 22 Jan 2006 02:48:07 +0200)

Juri Linkov wrote:

   > But, the problem is that building of Emacs proceeds even if
   > this message is shown:
   >
   > Pure Lisp storage overflow (approx. 1173352 bytes needed)

   This message is very easy to miss.

But when you then start Emacs you get the following difficult to miss
warning on your startup screen:

   Warning Warning  Pure space overflow  Warning Warning


   There is a special function `check_pure_size' to print a warning.  I tried
   to add it to this condition, but calling it directly from this condition
   prints warning messages too often, because when GC can't be done,
   Fgarbage_collect gets called repeatedly.

Showing it at startup should be sufficient for people to notice.
They noticed it this time: the bug got reported on emacs-pretest-bug.

Sincerely,

Luc.

  reply	other threads:[~2006-01-22  2:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-20  7:41 dump-emacs doesn't fail even if Pure Lisp storage overflows Kenichi Handa
2006-01-20 17:51 ` Stefan Monnier
2006-01-24 11:25   ` Kenichi Handa
2006-01-20 22:58 ` Richard M. Stallman
2006-01-22  0:48 ` Juri Linkov
2006-01-22  2:15   ` Luc Teirlinck [this message]
2006-01-22  3:19   ` Luc Teirlinck
2006-01-23  1:54     ` Juri Linkov
2006-01-22 17:44   ` Richard M. 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=200601220215.k0M2Ffs02046@raven.dms.auburn.edu \
    --to=teirllm@dms.auburn.edu \
    --cc=emacs-devel@gnu.org \
    --cc=handa@m17n.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).