From: LemonBreezes <look@strawberrytea.xyz>
To: "Eli Zaretskii" <eliz@gnu.org>
Cc: 65640@debbugs.gnu.org, Andrea Corallo <acorallo@gnu.org>
Subject: bug#65640: 30.0.50; segfault when building emacs with native-comp
Date: Fri, 01 Sep 2023 15:48:33 -0500 [thread overview]
Message-ID: <6f19eb4b-b6e7-49cd-8bb2-221597fa1394@app.fastmail.com> (raw)
In-Reply-To: <83a5u5by7e.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1241 bytes --]
Hi. I updated from the unstable GCC 13.2.1_p20230826 Gentoo package to the live 14.0.0.9999 version of GCC and the issue disappeared. Thank you. :))
On Fri, Sep 1, 2023, at 12:27 PM, Eli Zaretskii wrote:
> > Date: Fri, 01 Sep 2023 11:40:56 -0500
> > From: LemonBreezes <look@strawberrytea.xyz>
> > Cc: "Andrea Corallo" <acorallo@gnu.org>, 65640@debbugs.gnu.org
> >
> > Okay. So I can reproduce it by native-compiling org.el. But instead of Emacs segfaulting, I get the
> > following error:
> >
> > Debugger entered--Lisp error: (wrong-type-argument
> > "/home/st/.config/emacs/.local/straight/repos/org/l..." number-or-marker-p "Segmentation fault")
> > signal(wrong-type-argument ("/home/st/.config/emacs/.local/straight/repos/org/lisp/org.el"
> > number-or-marker-p "Segmentation fault"))
> > comp--native-compile("/home/st/.config/emacs/.local/straight/repos/org/l..." nil nil)
> > native-compile("/home/st/.config/emacs/.local/straight/repos/org/l...")
> > emacs-lisp-native-compile()
>
> Looks like Andrea was right: libgccjit is segfaulting on your system,
> for some reason. If some other version of libgccjit is known to work
> well on that platform, perhaps install that other version instead of
> what you have now.
>
[-- Attachment #2: Type: text/html, Size: 1949 bytes --]
next prev parent reply other threads:[~2023-09-01 20:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-30 19:38 bug#65640: 30.0.50; segfault when building emacs with native-comp StrawberryTea
2023-08-31 5:40 ` Eli Zaretskii
2023-08-31 7:24 ` Andrea Corallo
2023-09-01 15:05 ` LemonBreezes
2023-09-01 15:28 ` Eli Zaretskii
[not found] ` <0d10be97-ac8a-48b7-887e-1e9ae169daf2@app.fastmail.com>
2023-09-01 17:27 ` Eli Zaretskii
2023-09-01 20:48 ` LemonBreezes [this message]
2023-09-01 20:57 ` 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
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=6f19eb4b-b6e7-49cd-8bb2-221597fa1394@app.fastmail.com \
--to=look@strawberrytea.xyz \
--cc=65640@debbugs.gnu.org \
--cc=acorallo@gnu.org \
--cc=eliz@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 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).