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 19:20:32 +0300 [thread overview]
Message-ID: <837ezdiq3z.fsf@gnu.org> (raw)
In-Reply-To: <87vamx65x0.fsf@gmail.com> (message from Robert Pluim on Wed, 12 Jul 2017 17:17:31 +0200)
> From: Robert Pluim <rpluim@gmail.com>
> Date: Wed, 12 Jul 2017 17:17:31 +0200
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> From: Robert Pluim <rpluim@gmail.com>
> >> Date: Wed, 12 Jul 2017 16:47:57 +0200
> >> 62 992: CHAR[m] pos=9608 blev=0,btyp=L w=16 a+d=25+6 face=28 MB
> >> 63 1008: CHAR[ ] pos=9609 blev=0,btyp=L w=16 a+d=25+6 face=28 MB
> >> 64 1024: CHAR[i] pos=9610 blev=0,btyp=L w=16 a+d=25+6 face=28 MB
> >> 65 1040: CHAR[s] pos=9611 blev=0,btyp=L w=16 a+d=25+6 face=28 MB
> >> 66 1056: CHAR[ ] pos=9612 blev=0,btyp=L w=16 a+d=25+6 face=28 MB
> >> 67 1072: CHAR[a] pos=9613 blev=0,btyp=L w=16 a+d=25+6 face=28 MB
> >> 68 1088: CHAR[ ] pos=0 blev=0,btyp=B w=16 a+d=25+6 face=28 MB
> >> 69 1104: CHAR[s] pos=6237 blev=0,btyp=L w=16 a+d=25+6 MB
> >> 70 1120: CHAR[ ] pos=0 blev=0,btyp=B w=16 a+d=25+6 MB
> >> 71 1136: str=0xc8676d[9683324] w=-15971 a+d=147+0 MB PAD N/A [ slice=49485,147,0,0
> >> 72 -14835: str=0xc8671b[9683580] w=-15715 a+d=147+0 MB PAD AVOID [ slice=49741,147,0,0
> >> 74 -46113: CHAR[c] pos=9551 blev=0,btyp=L w=16 a+d=25+6 face=28 MB
> >
> > Does the text of this line give you enough hint to tell me what was on
> > this line? In particular, does it make sense that the line had 138
> > glyphs? Because it looks like everything after glyph 68 is garbage,
> > although I don't yet have any idea how it ended up there.
> >
>
> Yes, as I said it's line 237 of lisp/net/gnutls.el, it's definitely
> not 138 glyphs:
Well, I cannot know what kind of display features you have there; what
is just 63 characters in the file could have all kind of stuff
appended to it on display...
Anyway, what do these 2 show:
(gdb) p it->glyph_row->enabled_p
(gdb) p it->glyph_row->displays_text_p
Also, is the previous screen line OK? This will show:
(gdb) pgrowx (it->glyph_row-1)
Eventually, if nothing else gives a clue, please continue running
Emacs under GDB, and if the crashes are always in
compute_line_metrics, show the offending glyph_row each time it
crashes. Perhaps the data will give some hint about what could be
wrong. (Currently, the only idea I have is that somehow
glyph_row->used[1] is set to a value larger than it should, which
might mean some problem in maybe_produce_line_number, where it
increments the used count, but I'd like first to see if all the
problems manifest themselves with such a large used count.)
Thanks.
next prev parent reply other threads:[~2017-07-12 16:20 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 [this message]
2017-07-12 18:26 ` Robert Pluim
2017-07-12 19:01 ` Eli Zaretskii
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=837ezdiq3z.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 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.