unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Alan Third <alan@idiocy.org>
To: 房昌昊 <changhaoinfo@icloud.com>
Cc: 48460@debbugs.gnu.org
Subject: bug#48460: 27.2; Crash on M1 Mackook pro with GUI
Date: Sun, 16 May 2021 10:30:18 +0100	[thread overview]
Message-ID: <YKDmKhDUQEl2YGzW@breton.holly.idiocy.org> (raw)
In-Reply-To: <8EE756AB-7CE2-4ED1-9873-A4CA9A2962CA@icloud.com>

On Sun, May 16, 2021 at 11:58:45AM +0800, 房昌昊 via Bug reports for GNU Emacs, the Swiss army knife of text editors wrote:
> In GNU Emacs 27.2 (build 1, arm-apple-darwin20.3.0, NS appkit-2022.30 Version 11.2.3 (Build 20D91))
> of 2021-03-28 built on armbob.porkrind.org
> Windowing system distributor 'Apple', version 10.3.2022
> System Description:  macOS 11.3.1

> It works well with Command line. However, it crashs when I open it with
> GUI. It reports like the following:

> Exception Type:        EXC_BAD_INSTRUCTION (SIGABRT)
> Exception Codes:       0x0000000000000001, 0x0000000000000000
> Exception Note:        EXC_CORPSE_NOTIFY
> 
> Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
> 0   ???                           	0x00007ffe9467aab8 ???
> 1   libsystem_kernel.dylib        	0x00007fff2042f946 __pthread_kill + 10
> 2   libsystem_c.dylib             	0x00007fff20342be5 raise + 26
> 3   Emacs-x86_64-10_14            	0x00000001022626d9 terminate_due_to_signal + 153
> 4   Emacs-x86_64-10_14            	0x000000010226301b emacs_abort + 15
> 5   Emacs-x86_64-10_14            	0x000000010222a880 ns_term_shutdown + 80
> 6   Emacs-x86_64-10_14            	0x000000010211a5d4 shut_down_emacs + 340
> 7   Emacs-x86_64-10_14            	0x00000001022626a6 terminate_due_to_signal + 102
> 8   Emacs-x86_64-10_14            	0x000000010213ae8e handle_fatal_signal + 14
> 9   Emacs-x86_64-10_14            	0x000000010213af11 deliver_thread_signal + 129
> 10  Emacs-x86_64-10_14            	0x0000000102139969 deliver_fatal_thread_signal + 9
> 11  libsystem_platform.dylib      	0x00007fff204a3d7d _sigtramp + 29
> 12  ???                           	000000000000000000 0 + 0
> 13  Emacs-x86_64-10_14            	0x00000001021ff5c9 decode_time_components + 633
> 14  Emacs-x86_64-10_14            	0x00000001022000df decode_lisp_time + 159
> 15  Emacs-x86_64-10_14            	0x0000000102201240 Ftime_convert + 32

Well, I've never seen a crash like this before. I really have no idea
what could be causing it.

My only suggestion for now is to try another build. For example if you
have homebrew perhaps try the Emacs+ recipe?
-- 
Alan Third





  reply	other threads:[~2021-05-16  9:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-16  3:58 bug#48460: 27.2; Crash on M1 Mackook pro with GUI 房昌昊 via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-05-16  9:30 ` Alan Third [this message]
2021-06-24 16:20   ` Lars Ingebrigtsen

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=YKDmKhDUQEl2YGzW@breton.holly.idiocy.org \
    --to=alan@idiocy.org \
    --cc=48460@debbugs.gnu.org \
    --cc=changhaoinfo@icloud.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 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).