From: Alex <agrambot@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 28710@debbugs.gnu.org
Subject: bug#28710: 27.0.50; eassert failure in maybe_produce_line_number
Date: Mon, 09 Oct 2017 11:56:20 -0600 [thread overview]
Message-ID: <877ew4ciij.fsf@gmail.com> (raw)
In-Reply-To: <83376ssddj.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 09 Oct 2017 15:40:40 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
> Thanks. I installed a change that should fix the problem, please try
> the latest emacs-26 branch.
Looks like it's fixed, thanks.
> 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.
Unfortunately, when I try to use XFRAME, I get:
No symbol "__builtin_assume_aligned" in current context.
I tried the following workaround, but no backtraces showed up:
Thread 1 "emacs-26.0.60.4" hit Breakpoint 1, Fredraw_display ()
at dispnew.c:3032
3032 FOR_EACH_FRAME (tail, frame)
(gdb) n
3033 if (FRAME_VISIBLE_P (XFRAME (frame)))
(gdb) p (struct frame *) XLI(frame) - Lisp_Vectorlike
$3 = (struct frame *) 0x15c9285 <bss_sbrk_buffer+8055909>
(gdb) p $3->redisplay
$4 = false
(gdb) watch -l $3->redisplay
Hardware watchpoint 2: -location $3->redisplay
(gdb) commands
Type commands for breakpoint(s) 2, one per line.
End with a line saying just "end".
>bt
>continue
>end
(gdb) c
Continuing.
Thread 1 "emacs-26.0.60.4" received signal SIGABRT, Aborted.
next prev parent reply other threads:[~2017-10-09 17:56 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
2017-10-09 17:56 ` Alex [this message]
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=877ew4ciij.fsf@gmail.com \
--to=agrambot@gmail.com \
--cc=28710@debbugs.gnu.org \
--cc=eliz@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.