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: Mon, 09 Oct 2017 15:40:40 +0300 [thread overview]
Message-ID: <83376ssddj.fsf@gnu.org> (raw)
In-Reply-To: <87wp45z69y.fsf@gmail.com> (message from Alex on Sun, 08 Oct 2017 15:19:53 -0600)
> From: Alex <agrambot@gmail.com>
> Cc: 28710@debbugs.gnu.org
> Date: Sun, 08 Oct 2017 15:19:53 -0600
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > OK, so we need to understand the path the code takes after try_window
> > returns the value 1. This means, after typing "finish" 3 times, type
> > "next", then continue pressing RET until redisplay_window returns. I
> > need to see the path through the code until we exit redisplay_window
> > to understand where to put the missing call to clear_glyph_matrix.
>
> Thread 1 "emacs" hit Hardware watchpoint 2: -location $1->desired_matrix->rows->enabled_p
Thanks. I installed a change that should fix the problem, please try
the latest emacs-26 branch.
As to why this doesn't happen to me: for some reason, on your system,
when all the frame's windows have been redisplayed, their frame's
'redisplay' flag is set, and that causes redisplay_internal to
immediately redisplay all the windows again, see this part of your
transcript:
> 14320 if (!f_redisplay_flag && f->redisplay)
> (gdb)
> 14321 goto retry_frame;
On my system, the 'redisplay' flag stays reset, so this goto is
bypassed, and the problem doesn't happen. If you can afford one last
effort, please re-run the recipe with a watchpoint set on the frame's
'redisplay' flag, and show the backtraces from every one of the
watchpoint's hits, then perhaps I will know next time what else to try
to reproduce such cases.
Specifically, after invoking redraw-display, which causes GDB to kick
in, do this:
Thread 1 hit Breakpoint 3, Fredraw_display () at dispnew.c:3032
3032 FOR_EACH_FRAME (tail, frame)
(gdb) n
3033 if (FRAME_VISIBLE_P (XFRAME (frame)))
(gdb) p XFRAME(frame)
$1 = (struct frame *) 0x1b5e380 <dumped_data+4020672>
(gdb) p $1->redisplay
$2 = true
(gdb) watch -l $1->redisplay
Hardware watchpoint 4: -location $1->redisplay
(gdb) commands
> bt
> continue
> end
(gdb) continue
and then continue with the recipe, and show all the backtraces you get.
next prev parent reply other threads:[~2017-10-09 12:40 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83376ssddj.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 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.