From: Eli Zaretskii <eliz@gnu.org>
To: Jake Goulding <jake.goulding@gmail.com>
Cc: 30320@debbugs.gnu.org
Subject: bug#30320: 26.0.91; Crash when using lsp-ui-doc-mode
Date: Thu, 01 Feb 2018 19:16:19 +0200 [thread overview]
Message-ID: <83po5oeil8.fsf@gnu.org> (raw)
In-Reply-To: <CAEDNNqAQn6Si_T0he16B3Xf=1SSUpxz2DyT3j-V1X+YS1+3tnQ@mail.gmail.com> (message from Jake Goulding on Thu, 1 Feb 2018 10:10:42 -0500)
> From: Jake Goulding <jake.goulding@gmail.com>
> 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.
next prev parent reply other threads:[~2018-02-01 17:16 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-01 15:10 bug#30320: 26.0.91; Crash when using lsp-ui-doc-mode Jake Goulding
2018-02-01 17:16 ` Eli Zaretskii [this message]
2018-02-01 19:52 ` Jake Goulding
2018-02-01 19:54 ` Jake Goulding
2018-02-02 8:21 ` Eli Zaretskii
2018-02-02 16:22 ` Jake Goulding
2018-02-03 9:04 ` martin rudalics
2018-02-03 16:10 ` Jake Goulding
2018-02-03 16:34 ` Eli Zaretskii
2018-02-03 19:43 ` Jake Goulding
2018-02-03 20:10 ` Eli Zaretskii
2018-02-03 21:55 ` Jake Goulding
2018-02-04 18:35 ` Eli Zaretskii
2018-02-04 21:08 ` Jake Goulding
2018-02-04 21:38 ` Jake Goulding
2018-02-05 17:03 ` Eli Zaretskii
2018-02-05 18:43 ` Jake Goulding
2018-02-05 20:14 ` Eli Zaretskii
2018-02-06 9:29 ` martin rudalics
2018-02-10 10:14 ` Eli Zaretskii
2018-02-10 10:45 ` martin rudalics
2018-02-10 12:11 ` Eli Zaretskii
2018-02-10 13:40 ` martin rudalics
2018-02-10 16:38 ` Eli Zaretskii
2018-02-11 9:36 ` martin rudalics
2018-02-11 15:43 ` Eli Zaretskii
2018-02-12 1:31 ` Jake Goulding
2018-02-12 1:33 ` Jake Goulding
2018-02-12 1:48 ` Jake Goulding
2018-02-12 9:24 ` martin rudalics
2019-10-30 11:06 ` Lars Ingebrigtsen
2018-02-12 9:22 ` martin rudalics
2018-02-12 9:22 ` martin rudalics
2018-02-12 9:22 ` martin rudalics
2018-02-12 18:04 ` Eli Zaretskii
2018-02-10 19:04 ` Jake Goulding
2018-02-02 8:27 ` martin rudalics
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=83po5oeil8.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=30320@debbugs.gnu.org \
--cc=jake.goulding@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.