all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: LemonBreezes <look@strawberrytea.xyz>
Cc: 65640@debbugs.gnu.org, acorallo@gnu.org
Subject: bug#65640: 30.0.50; segfault when building emacs with native-comp
Date: Fri, 01 Sep 2023 18:28:42 +0300	[thread overview]
Message-ID: <83edjhc3px.fsf@gnu.org> (raw)
In-Reply-To: <76c3d882-fa35-46a5-8df0-505c2815d18c@app.fastmail.com> (message from LemonBreezes on Fri, 01 Sep 2023 10:05:52 -0500)

> Date: Fri, 01 Sep 2023 10:05:52 -0500
> From: LemonBreezes <look@strawberrytea.xyz>
> Cc: 65640@debbugs.gnu.org
> 
> Okay. So I noticed that even though Emacs was running, the native
> compiler was segfaulting in the background. So I recompiled Emacs with
> GCC and no optimizations nor patches and I still see that native compilation is
> segfaulting on org-element.el. I have attached some verbose logs:
> https://0x0.st/HpjT.txt
> 
> I don't know how to get a backtrace. If I run Emacs with GDB, libgccjit
> gives me a segfault in the *Async-native-compile-log* but Emacs itself
> does not segfault.

What happens if you compile org-element.el by invoking
emacs-lisp-native-compile?  That is:

  emacs -Q
  C-x C-f lisp/org/org-element.el RET
  M-x emacs-lisp-native-compile RET

Does Emacs crash if you do the above?  If so, run the above under GDB,
and show the backtrace.

Thanks.





  reply	other threads:[~2023-09-01 15:28 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 [this message]
     [not found]         ` <0d10be97-ac8a-48b7-887e-1e9ae169daf2@app.fastmail.com>
2023-09-01 17:27           ` Eli Zaretskii
2023-09-01 20:48             ` LemonBreezes
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83edjhc3px.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=65640@debbugs.gnu.org \
    --cc=acorallo@gnu.org \
    --cc=look@strawberrytea.xyz \
    /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.