From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: 66098@debbugs.gnu.org, rpluim@gmail.com, acorallo@gnu.org
Subject: bug#66098: Crash in itree.c on macOS with incomplete backtrace
Date: Sun, 24 Sep 2023 15:10:38 +0300 [thread overview]
Message-ID: <83sf733h6p.fsf@gnu.org> (raw)
In-Reply-To: <CADwFkmm+pxS4b+nPGWLQs0OeYbnzkEJOSgghbMpFNMqqEchfSw@mail.gmail.com> (message from Stefan Kangas on Sun, 24 Sep 2023 03:55:17 -0700)
> From: Stefan Kangas <stefankangas@gmail.com>
> Date: Sun, 24 Sep 2023 03:55:17 -0700
> Cc: rpluim@gmail.com, 66098@debbugs.gnu.org, Andrea Corallo <acorallo@gnu.org>
>
> Find below the Apple crash log, which says something about trampoline
> and native_elisp_load. Unfortunately, the below crash happened in an
> optimized build.
Looks like infinite recursion of some sorts? The function at
0x7fb2d9463cb3 calls itself again and again.
Are you saying that the problem doesn't happen without
native-compilation?
next prev parent reply other threads:[~2023-09-24 12:10 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-19 8:47 bug#66098: Crash in itree.c on macOS with incomplete backtrace Stefan Kangas
2023-09-19 9:23 ` Robert Pluim
2023-09-19 10:09 ` Robert Pluim
2023-09-20 8:08 ` Paul Eggert
2023-09-20 8:22 ` Robert Pluim
2023-09-22 10:58 ` Stefan Kangas
2023-09-22 12:07 ` Robert Pluim
2023-09-23 13:02 ` Stefan Kangas
2023-09-25 8:36 ` Robert Pluim
2023-09-19 11:24 ` Eli Zaretskii
2023-09-22 10:51 ` Stefan Kangas
2023-09-22 12:36 ` Eli Zaretskii
2023-09-22 12:46 ` Robert Pluim
2023-09-23 11:56 ` Stefan Kangas
2023-09-23 12:42 ` Eli Zaretskii
2023-09-24 10:55 ` Stefan Kangas
2023-09-24 12:10 ` Eli Zaretskii [this message]
2023-09-24 12:25 ` Stefan Kangas
2023-09-24 21:01 ` Stefan Kangas
2023-09-25 3:38 ` Gerd Möllmann
2023-09-19 11:42 ` Gerd Möllmann
2023-09-19 12:21 ` Gerd Möllmann
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=83sf733h6p.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=66098@debbugs.gnu.org \
--cc=acorallo@gnu.org \
--cc=rpluim@gmail.com \
--cc=stefankangas@gmail.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.