From: Eli Zaretskii <eliz@gnu.org>
To: Alex <agrambot@gmail.com>
Cc: 28710@debbugs.gnu.org
Subject: bug#28710: 27.0.50; eassert failure in maybe_produce_line_number
Date: Thu, 05 Oct 2017 11:30:26 +0300 [thread overview]
Message-ID: <83d162xahp.fsf@gnu.org> (raw)
In-Reply-To: <8760buwnne.fsf@gmail.com> (message from Alex on Wed, 04 Oct 2017 16:31:33 -0600)
> From: Alex <agrambot@gmail.com>
> Date: Wed, 04 Oct 2017 16:31:33 -0600
>
> 1. Open up a diff in magit (e.g., M-x magit-status then RET on the first
> line).
> 2. Press RET on an added line.
> 3. In the opened buffer, do M-: (setq display-line-numbers t)
> 4. C-x b RET
> 5. Press RET on the line again.
It doesn't crash for me here. But since it's hardly repeatable for
you, I'm not surprised.
> #2 0x00000000006233ad in die (msg=0x72ad60 "it->glyph_row == NULL || it->glyph_row->used[TEXT_AREA] == 0", file=0x726c3d "xdisp.c", line=21061) at alloc.c:7419
> #3 0x0000000000483af6 in maybe_produce_line_number (it=0x7ffef1f01900) at xdisp.c:21061
If you go to frame #3, in maybe_produce_line_number, and type
(gdb) pgrowx it->glyph_row
what does that produce? (You will need to source src/.gdbinit for the
pgrowx command to work.)
Btw, your recipe didn't quite work for me: the first step failed when
I pressed RET "on the first line" of the buffer presented by "M-x
magit-status" in the current release branch tip. It said there was
nothing to show about that line. I needed to find a suitable line
further down in the buffer. Am I missing something here? Can you
specify precise steps, assuming I know nothing about using Magit?
Thanks.
next prev parent reply other threads:[~2017-10-05 8:30 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-04 22:31 bug#28710: 27.0.50; eassert failure in maybe_produce_line_number Alex
2017-10-05 8:30 ` Eli Zaretskii [this message]
2017-10-05 23:51 ` Alex
2017-10-06 8:38 ` Eli Zaretskii
2017-10-07 23:05 ` Alex
2017-10-08 6:29 ` Eli Zaretskii
2017-10-08 7:11 ` Alex
2017-10-08 9:35 ` Eli Zaretskii
2017-10-08 10:09 ` Eli Zaretskii
2017-10-09 13:03 ` Eli Zaretskii
2017-10-08 19:05 ` Alex
2017-10-08 19:50 ` Eli Zaretskii
2017-10-08 21:19 ` Alex
2017-10-09 12:40 ` Eli Zaretskii
2017-10-09 17:56 ` Alex
2017-10-09 18:51 ` Eli Zaretskii
2017-10-09 19:36 ` Alex
2017-10-10 6:21 ` 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=83d162xahp.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=28710@debbugs.gnu.org \
--cc=agrambot@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 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).