From: Robert Pluim <rpluim@gmail.com>
To: 27668@debbugs.gnu.org
Subject: bug#27668: 26.0.50; Crash with display-line-numbers t
Date: Fri, 14 Jul 2017 11:47:03 +0200 [thread overview]
Message-ID: <87vamvqrjc.fsf@gmail.com> (raw)
In-Reply-To: <87k23d7ovv.fsf@gmail.com>
Robert Pluim <rpluim@gmail.com> writes:
> Eli Zaretskii <eliz@gnu.org> writes:
>
>>> From: Robert Pluim <rpluim@gmail.com>
>>> (gdb) pgrowx it->glyph_row
>>> TEXT: 66 glyphs
>>> 0 0: CHAR[ ] pos=-1 blev=2,btyp=EN w=16 a+d=25+6 face=51 MB AVOID
>>> 1 16: CHAR[1] pos=-1 blev=2,btyp=EN w=16 a+d=25+6 face=51 MB AVOID
>>> 2 32: CHAR[2] pos=-1 blev=2,btyp=EN w=16 a+d=25+6 face=51 MB AVOID
>>> 3 48: CHAR[6] pos=-1 blev=2,btyp=EN w=16 a+d=25+6 face=51 MB AVOID
>>> 4 64: CHAR[1] pos=-1 blev=2,btyp=EN w=16 a+d=25+6 face=51 MB AVOID
>>> 5 80: CHAR[ ] pos=-1 blev=2,btyp=EN w=16 a+d=25+6 face=51 MB AVOID
>>> 6 96: CHAR[ ] pos=37180 blev=0,btyp=L w=16 a+d=25+6 MB
>>
>> Hmm... I'm not sure how this happened, but I have a theory. I've now
>> made a change in master based on that theory, and also added an
>> assertion where you previously had to set a breakpoint. Please see if
>> the current master fixes the problem and doesn't hit the assertion in
>> maybe_produce_line_number.
>
> git describe HEAD
> emacs-24.5-rc3-fixed-13053-g60d24e1681
All this TLS discussion has at least yielded something useful: a reproduction
recipe:
src/emacs -Q
; Put the following in *scratch*
(setq display-line-number t)
C-x C-e
M-x eww https://revoked.badssl.com/
q
*boom*
Regards
Robert
next prev parent reply other threads:[~2017-07-14 9:47 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
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 [this message]
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=87vamvqrjc.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=27668@debbugs.gnu.org \
--cc=bug-gnu-emacs@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).