From: Eli Zaretskii <eliz@gnu.org>
To: 27668@debbugs.gnu.org
Subject: bug#27668: 26.0.50; Crash with display-line-numbers t
Date: Wed, 12 Jul 2017 22:01:28 +0300 [thread overview]
Message-ID: <834luhiinr.fsf@gnu.org> (raw)
In-Reply-To: <871spl5x5h.fsf@gmail.com> (message from Robert Pluim on Wed, 12 Jul 2017 20:26:50 +0200)
> From: Robert Pluim <rpluim@gmail.com>
> Date: Wed, 12 Jul 2017 20:26:50 +0200
>
> 125 2000: CHAR[r] pos=9542 blev=0,btyp=L w=16 a+d=25+6 face=28 MB
> 126 2016: CHAR[e] pos=9543 blev=0,btyp=L w=16 a+d=25+6 face=28 MB
> 127 2032: CHAR[s] pos=9544 blev=0,btyp=L w=16 a+d=25+6 face=28 MB
> 128 2048: CHAR[e] pos=9545 blev=0,btyp=L w=16 a+d=25+6 face=28 MB
> 129 2064: CHAR[n] pos=9546 blev=0,btyp=L w=16 a+d=25+6 face=28 MB
> 130 2080: CHAR[t] pos=9547 blev=0,btyp=L w=16 a+d=25+6 face=28 MB
> 131 2096: CHAR[e] pos=9548 blev=0,btyp=L w=16 a+d=25+6 face=28 MB
> 132 2112: CHAR[d] pos=9549 blev=0,btyp=L w=16 a+d=25+6 face=28 MB
> 133 2128: CHAR[ ] pos=0 blev=0,btyp=B w=16 a+d=25+6 face=28 MB
>
> Hmm. Is it normal for the text on that line to be shown twice here?
No, of course not. Everything beyond the first glyph whose pos is
zero (that's the glyph that stands for the newline, it is there so we
could put the cursor at EOL) shouldn't be there.
> The crash is always in compute_line_metrics. I'll continue to run
> under gdb, and see if I can find a recipe.
If it's always in compute_line_metrics, then please see if the value
of row->used[1] is always about twice the correct one. If it is,
perhaps we will be able to come up with a breakpoint or watchpoint
condition that will catch the code which is responsible.
next prev parent reply other threads:[~2017-07-12 19:01 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-12 13:42 bug#27668: 26.0.50; Crash with display-line-numbers t Robert Pluim
2017-07-12 14:34 ` Eli Zaretskii
2017-07-12 14:47 ` Robert Pluim
2017-07-12 15:05 ` Eli Zaretskii
2017-07-12 15:17 ` Robert Pluim
2017-07-12 16:20 ` Eli Zaretskii
2017-07-12 18:26 ` Robert Pluim
2017-07-12 19:01 ` Eli Zaretskii [this message]
2017-07-13 8:28 ` Robert Pluim
2017-07-13 16:24 ` Eli Zaretskii
2017-07-13 16:33 ` Robert Pluim
2017-07-13 16:29 ` Eli Zaretskii
2017-07-13 16:42 ` Robert Pluim
2017-07-13 17:56 ` Eli Zaretskii
2017-07-13 18:17 ` Robert Pluim
2017-07-13 19:22 ` Eli Zaretskii
2017-07-13 19:35 ` Robert Pluim
2017-07-14 8:03 ` Eli Zaretskii
2017-07-14 8:59 ` Robert Pluim
2017-07-14 9:47 ` Robert Pluim
2017-07-14 10:04 ` Eli Zaretskii
2017-07-14 11:36 ` Robert Pluim
2017-07-14 12:39 ` Eli Zaretskii
2017-07-14 9:51 ` Eli Zaretskii
2017-07-14 11:45 ` Robert Pluim
2017-07-14 13:28 ` Eli Zaretskii
2017-07-14 14:47 ` Robert Pluim
2017-07-14 15:07 ` Robert Pluim
2017-07-14 15:14 ` Eli Zaretskii
2017-07-17 14:38 ` Robert Pluim
2017-07-17 15:34 ` Eli Zaretskii
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=834luhiinr.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=27668@debbugs.gnu.org \
/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).