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: Fri, 02 Feb 2018 10:21:49 +0200 [thread overview]
Message-ID: <83a7wrer8i.fsf@gnu.org> (raw)
In-Reply-To: <CAEDNNqBe6WNpKxGQp6m-Twj1PCVyqRYUg9-9yj8Rj3CRFfn8dg@mail.gmail.com> (message from Jake Goulding on Thu, 1 Feb 2018 14:52:59 -0500)
> From: Jake Goulding <jake.goulding@gmail.com>
> Date: Thu, 1 Feb 2018 14:52:59 -0500
> Cc: 30320@debbugs.gnu.org
>
> It looks like `curY (tty) >= FrameRows (tty) - 1`:
>
> (lldb)
> frame #9: 0x0000000100173380 Emacs`cmcheckmagic(tty=0x000000010180d000) at cm.c:118
> 115 if (curX (tty) == FrameCols (tty))
> 116 {
> 117 if (!MagicWrap (tty) || curY (tty) >= FrameRows (tty) - 1)
> -> 118 emacs_abort ();
> 119 if (tty->termscript)
> 120 putc_unlocked ('\r', tty->termscript);
> 121 putc_unlocked ('\r', tty->output);
> (lldb) p (tty)->Wcm->cm_magicwrap
> (bool_bf) $0 = true
> (lldb) p (tty)->Wcm->cm_curY
> (int) $1 = 2
> (lldb) p (tty)->Wcm->cm_rows
> (int) $2 = 3
Hmm... is it reasonable that the TTY frame has only 3 rows? That's an
awfully small frame, and maybe Emacs is unable to work correctly with
such small frames. It doesn't justify a crash, but I'm trying to
establish whether this is the root cause of the problem, or maybe
Emacs became confused wrt the frame size.
next prev parent reply other threads:[~2018-02-02 8:21 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
2018-02-01 19:52 ` Jake Goulding
2018-02-01 19:54 ` Jake Goulding
2018-02-02 8:21 ` Eli Zaretskii [this message]
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=83a7wrer8i.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.