From: Stefan Kangas <stefankangas@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>,
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: Tue, 24 Dec 2024 02:50:02 +0000 [thread overview]
Message-ID: <CADwFkmkwvVV4R_Vfhqd0D7av36ppnkj8f2m-1YpVwsnfJJgLvw@mail.gmail.com> (raw)
In-Reply-To: <86h67cddoc.fsf@gnu.org>
tags 74744 + pending
thanks
Eli Zaretskii <eliz@gnu.org> writes:
>> Date: Mon, 9 Dec 2024 16:23:56 +0100
>> Cc: 74744@debbugs.gnu.org
>> From: Eric Marsden <eric.marsden@risk-engineering.org>
>>
>> On 09/12/2024 16:03, Eli Zaretskii wrote:
>> > And if you enlarge PURESIZE, does the segfault go away?
>> >
>> > Also, please try without --enable-link-time-optimization and without
>> > the -flto=8 -ffat-lto-objects compiler options.
>>
>> Thanks, inspired by Pip's suggestion I used
>>
>> ./configure --with-options
>> make FAST=true bootstrap
>>
>> which worked, so I have not investigated further. I was not anticipating
>> that the default make recipe might fail due to pre-existing object files.
>
> Yes, pure space can overflow if loadup loads byte-compiled files.
> This is a known subtlety that sometimes pops up.
Given that we are planning to remove pure space, maybe this bug should
be closed. I'm tagging it as pending for now.
next prev parent reply other threads:[~2024-12-24 2:50 UTC|newest]
Thread overview: 6+ 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
2024-12-09 15:03 ` Eli Zaretskii
[not found] ` <43753bef-994f-4a90-9867-ab9f9fc112e0@risk-engineering.org>
2024-12-09 16:27 ` Eli Zaretskii
2024-12-24 2:50 ` Stefan Kangas [this message]
2025-01-02 1:51 ` Stefan Kangas
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=CADwFkmkwvVV4R_Vfhqd0D7av36ppnkj8f2m-1YpVwsnfJJgLvw@mail.gmail.com \
--to=stefankangas@gmail.com \
--cc=74744@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=eric.marsden@risk-engineering.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.