From: "Gerd Möllmann" <gerd.moellmann@gmail.com>
To: Sean Devlin <spd@toadstyle.org>
Cc: 74966@debbugs.gnu.org, Pip Cet <pipcet@protonmail.com>
Subject: bug#74966: 31.0.50; Crash report (using igc on macOS)
Date: Thu, 19 Dec 2024 11:25:12 +0100 [thread overview]
Message-ID: <m28qscgebb.fsf@gmail.com> (raw)
In-Reply-To: <EB94DB86-0A28-4D3C-8694-173387DA909C@toadstyle.org> (Sean Devlin's message of "Thu, 19 Dec 2024 18:17:51 +0900")
Sean Devlin <spd@toadstyle.org> writes:
> Hi folks,
>
> I was using Emacs and encountered a crash.
>
> I am running on macOS, and I built Emacs from scratch/igc using the
> instructions on that branch.
>
> I didn’t have Emacs running under a debugger, but I do have some crash
> information captured by macOS. (See attached.)
>
> At the time, I was trying to use apropos-documentation. I invoked the
> command once, entered a string, and hit RET, and it signaled an error. I
> tried to do this again and Emacs crashed.
>
> I hope this is useful. Please let me know if there’s any other
> information I can collect.
>
> Thanks!
>
.c:1811)
> 11 Emacs 0x100d222a4 handle_sigsegv + 64 (sysdep.c:1949)
> 12 libsystem_platform.dylib 0x19435ee04 _sigtramp + 56
> 13 apropos-7c1ecbdf-5d074552.eln 0x103407010 F6170726f706f732d736166652d646f63756d656e746174696f6e_apropos_safe_documentation_0 + 208
> 14 Emacs 0x100dd0a4c exec_byte_code + 2648 (bytecode.c:828)
> 15 Emacs 0x100d82488 Ffuncall + 456 (eval.c:3099)
> 16 apropos-7c1ecbdf-5d074552.eln 0x103405968 F6170726f706f732d2d6d61702d7072656c6f616465642d61746f6d73_apropos__map_preloaded_atoms_0 + 696
Looks to me like apropos-safe-documentation, native compiled, has a
problem here and gets an EXC_BAD_ACCESS. But that's all I can see. It's
not even clear to me if this is GC-related or not.
Can you reproduce this? If yes, can you give me a recipe?
Pip, should I perhaps merge with current master? I think there have been
fixes to the native compiler on master, not sure though.
next prev parent reply other threads:[~2024-12-19 10:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-19 9:17 bug#74966: 31.0.50; Crash report (using igc on macOS) Sean Devlin
[not found] ` <handler.74966.B.173459989517154.ack@debbugs.gnu.org>
2024-12-19 9:21 ` bug#74966: Acknowledgement (31.0.50; Crash report (using igc on macOS)) Sean Devlin
2024-12-19 10:28 ` Gerd Möllmann
2024-12-19 11:05 ` Sean Devlin
2024-12-19 11:30 ` Gerd Möllmann
2024-12-19 10:25 ` Gerd Möllmann [this message]
2024-12-19 11:57 ` bug#74966: 31.0.50; Crash report (using igc on macOS) Sean Devlin
2024-12-19 11:48 ` Pip Cet via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-19 11:54 ` Sean Devlin
2024-12-19 14:02 ` Gerd Möllmann
2024-12-19 14:07 ` Pip Cet via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=m28qscgebb.fsf@gmail.com \
--to=gerd.moellmann@gmail.com \
--cc=74966@debbugs.gnu.org \
--cc=pipcet@protonmail.com \
--cc=spd@toadstyle.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).