Subject: Re: bug#30320: 26.0.91; Crash when using lsp-ui-doc-mode

From: Eli Zaretskii <[email-masked]>
Date: Thu, 01 Feb 2018 19:16:19 +0200

> From: Jake Goulding <[email-masked]>
> Date: Thu, 1 Feb 2018 10:10:42 -0500
> 
> Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
> 0   libsystem_kernel.dylib        0x00007fff5c930e3e __pthread_kill + 10
> 1   libsystem_pthread.dylib        0x00007fff5ca6f150 pthread_kill + 333
> 2   libsystem_c.dylib              0x00007fff5c83f8fe raise + 26
> 3   org.gnu.Emacs                  0x000000010009ed1e terminate_due_to_signal + 152
> 4   org.gnu.Emacs                  0x00000001000b6961 emacs_abort + 19
> 5   org.gnu.Emacs                  0x000000010016ea86 ns_term_shutdown + 122
> 6   org.gnu.Emacs                  0x000000010009eee0 shut_down_emacs + 262
> 7   org.gnu.Emacs                  0x000000010009ecec terminate_due_to_signal + 102
> 8   org.gnu.Emacs                  0x00000001000b6961 emacs_abort + 19
> 9   org.gnu.Emacs                  0x000000010008b814 cmcheckmagic + 136

Can you run Emacs under a debugger and tell which part of the
condition below cause the call to emacs_abort?

  void
  cmcheckmagic (struct tty_display_info *tty)
  {
    if (curX (tty) == FrameCols (tty))
      {
	if (!MagicWrap (tty) || curY (tty) >= FrameRows (tty) - 1)
	  emacs_abort ();

Also, was the original cause also in "emacs -nw", or was it in a GUI
frame?  If the latter, please show the backtrace from that crash as
well.

Thanks.