all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Pip Cet via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eric Marsden <eric.marsden@risk-engineering.org>
Cc: 74744@debbugs.gnu.org
Subject: bug#74744: Build failure: SEGV in temacs (with "Pure Lisp storage overflowed")
Date: Mon, 09 Dec 2024 12:41:47 +0000	[thread overview]
Message-ID: <87zfl5ghae.fsf@protonmail.com> (raw)
In-Reply-To: <7b99adb7-ce18-4454-a84c-e346d611ab71@risk-engineering.org>

"Eric Marsden" <eric.marsden@risk-engineering.org> writes:

> Hello,
> Building current HEAD (6df535788a20c9047d33dd8a0c62258597632647) on Linux/AMD64 fails with a SEGV.
> I see that there is a "Pure Lisp storage overflowed" message which is perhaps related.

Yes, crashes after purespace overflow are currently expected, and they
regularly happen if you build in a directory that has .elc files from
previous builds in it.

If `make bootstrap' (which removes the .elc files) doesn't help, please
find out by how much you need to increase BASE_PURESIZE in puresize.h
for the build to succeed.

(There's some logic in the Emacs sources that would calculate the number
for you, but that's also broken and has been for ages, so you'll have to
experiment.)

Sorry that the poor state of the Emacs source code forces you to waste
your time on rediscovering well-known bugs.

Pip






  reply	other threads:[~2024-12-09 12:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-09 10:48 bug#74744: Build failure: SEGV in temacs (with "Pure Lisp storage overflowed") Eric Marsden
2024-12-09 12:41 ` Pip Cet via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2024-12-09 15:03 ` Eli Zaretskii
     [not found]   ` <43753bef-994f-4a90-9867-ab9f9fc112e0@risk-engineering.org>
2024-12-09 16:27     ` Eli Zaretskii

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=87zfl5ghae.fsf@protonmail.com \
    --to=bug-gnu-emacs@gnu.org \
    --cc=74744@debbugs.gnu.org \
    --cc=eric.marsden@risk-engineering.org \
    --cc=pipcet@protonmail.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.