GNU bug report logs -
#31848
[macOS] M-x server-start crashes if extraneous server file exists
Previous Next
Reported by: Tim Harper <timcharper <at> gmail.com>
Date: Fri, 15 Jun 2018 17:31:03 UTC
Severity: normal
Tags: moreinfo
Merged with 32376
Found in version 26.1
Done: Lars Ingebrigtsen <larsi <at> gnus.org>
Bug is archived. No further changes may be made.
Full log
Message #8 received at 31848 <at> debbugs.gnu.org (full text, mbox):
> From: Tim Harper <timcharper <at> gmail.com>
> Date: Fri, 15 Jun 2018 11:15:05 -0600
>
> Emacs on OS X crashes when stale server auth file is present. To reproduce:
>
> 1) Start Emacs 26.1
> 2) Run server-start
> 3) Copy the file `server` in the {server-auth-dir} folder to `server-2`
> 4) Quit Emacs
> 5) Rename `server-2` file to `server`
> 6) Relaunch Emacs
> 7) Run server-start
> 8) Observe crash
It doesn't crash here, but I'm not on macOS.
> Crash report:
>
> Process: Emacs-x86_64-10_10 [54595]
> Path: /Applications/Emacs.app/Contents/MacOS/Emacs-x86_64-10_10
> Identifier: org.gnu.Emacs
> Version: Version 26.1 (9.0)
> Code Type: X86-64 (Native)
> Parent Process: ??? [1]
> Responsible: Emacs-x86_64-10_10 [54595]
> User ID: 501
>
> Date/Time: 2018-06-15 11:11:33.871 -0600
> OS Version: Mac OS X 10.13.4 (17E199)
> Report Version: 12
> Anonymous UUID: FAFB472E-6635-1BF9-3A87-39490D81E931
>
> Sleep/Wake UUID: 62FC5A60-36B2-453C-832A-C3FD5AA072DE
>
> Time Awake Since Boot: 180000 seconds
> Time Since Wake: 12000 seconds
>
> System Integrity Protection: disabled
>
> Crashed Thread: 0 Dispatch queue: com.apple.main-thread
>
> Exception Type: EXC_BAD_ACCESS (SIGABRT)
> Exception Codes: KERN_INVALID_ADDRESS at 0x000000000000003f
> Exception Note: EXC_CORPSE_NOTIFY
>
> VM Regions Near 0x3f:
> -->
> __TEXT 0000000100000000-0000000100233000 [ 2252K] r-x/rwx SM=COW /Applications/Emacs.app/Contents/MacOS/Emacs-x86_64-10_10
>
> Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
> 0 libsystem_kernel.dylib 0x00007fff654e5b6e __pthread_kill + 10
> 1 libsystem_pthread.dylib 0x00007fff656b0080 pthread_kill + 333
> 2 libsystem_c.dylib 0x00007fff653f36fe raise + 26
> 3 Emacs-x86_64-10_10 0x00000001000c0a81 terminate_due_to_signal + 161
> 4 Emacs-x86_64-10_10 0x00000001000dde43 emacs_abort + 19
> 5 Emacs-x86_64-10_10 0x00000001001c4a0c ns_term_shutdown + 124
> 6 Emacs-x86_64-10_10 0x00000001000c0c55 shut_down_emacs + 261
> 7 Emacs-x86_64-10_10 0x00000001000c0a46 terminate_due_to_signal + 102
> 8 Emacs-x86_64-10_10 0x00000001000df736 deliver_fatal_thread_signal + 134
> 9 Emacs-x86_64-10_10 0x00000001000e0b8a handle_sigsegv + 170
> 10 libsystem_platform.dylib 0x00007fff656a3f5a _sigtramp + 26
> 11 ??? 000000000000000000 0 + 0
> 12 Emacs-x86_64-10_10 0x0000000100146a67 funcall_subr + 247
> 13 Emacs-x86_64-10_10 0x0000000100146114 Ffuncall + 740
Can you tell what Lisp function is being called here?
This bug report was last modified 4 years and 277 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.