all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Kenichi Handa <handa@m17n.org>
Cc: emacs-unicode@gnu.org, duncanmak@gmail.com, emacs-devel@gnu.org
Subject: Re: Crash building unicode2, NSTATICS too low, pure space overflow.
Date: Thu, 03 Aug 2006 16:36:10 +0900	[thread overview]
Message-ID: <E1G8XkY-0005Zr-00@etlken> (raw)
In-Reply-To: <44D19F77.4050904@swipnet.se> (message from Jan Djärv on Thu, 03	Aug 2006 09:02:15 +0200)

In article <44D19F77.4050904@swipnet.se>, Jan Djärv <jan.h.d@swipnet.se> writes:

> Am I the only one that sees this:
> `/bin/pwd`/temacs --batch --load loadup bootstrap
> make[2]: *** [bootstrap-emacs] Avbruten (SIGABRT)
> make[2]: Leaving directory `/home/jhd/src/emacs-unicode2/src'
> make[1]: *** [bootstrap-build] Fel 2
> make[1]: Leaving directory `/home/jhd/src/emacs-unicode2'
> make: *** [bootstrap] Fel 2

> It aborts here (alloc.c):

> 4844    staticpro (varaddress)
> 4845         Lisp_Object *varaddress;
> 4846    {
> 4847      staticvec[staticidx++] = varaddress;
> 4848      if (staticidx >= NSTATICS)
> 4849        abort ();
> 4850    }

I recently got the same bug report from Duncan
<duncanmak@gmail.com>.  As I usually build Emacs without
gtk, I didn't notice it.  Without gtk and with
enable-font-backend, staticidx reaches 1279!  In HEAD, it
reaches 1193.

> If I increase NSTATICS to 1281 it does not abort.  This is with GTK.  When 
> compiling with GTK an extra gtk-version-string is staticpro:ed, so compiling 
> without GTK does not abort.  I also get (GTK or non-GTK version):

> emacs:0:Pure Lisp storage overflow (approx. 1211344 bytes needed)

I don't see that in non-GKT version, though.  The last step
of dumping shows this message.

Dumping under names emacs and emacs-23.0.0.6
1209872 pure bytes used

> Is it OK to just increase NSTATICS a bit?  Shouldn't staticvec be dynamically 
> allocated BTW?

It was increased from 1026 to 1280 about 4 years ago.
Perhaps there was a good reason for not chaning it to be
allocated dynamically ... I'm not sure.

1026 is 0x402, 1280 is 0x500.  What is the good value for
NSTATICS this time; 0x600 or 0x602?

---
Kenichi Handa
handa@m17n.org

       reply	other threads:[~2006-08-03  7:36 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1G7kSB-0000Mi-00@etlken>
     [not found] ` <44D19F77.4050904@swipnet.se>
2006-08-03  7:36   ` Kenichi Handa [this message]
2006-08-03 10:01     ` Crash building unicode2, NSTATICS too low, pure space overflow Jan Djärv
2006-08-03 19:15     ` Richard Stallman
2006-08-04  0:58       ` Kenichi Handa
2006-08-04  4:58         ` Richard Stallman
2006-08-07  6:24         ` Jan Djärv
2006-08-07  6:46           ` Kenichi Handa
2006-08-04  9:09       ` Andreas Schwab
2006-08-04  9:29         ` Duncan Mak
2006-08-04 10:05           ` David Kastrup
2006-08-04 16:14             ` Duncan Mak
2006-08-04 18:42         ` 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=E1G8XkY-0005Zr-00@etlken \
    --to=handa@m17n.org \
    --cc=duncanmak@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=emacs-unicode@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 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.