From: Eli Zaretskii <eliz@gnu.org>
To: martin rudalics <rudalics@gmx.at>
Cc: 18597@debbugs.gnu.org
Subject: bug#18597: 25.0.50; Assertion violation in reseat_1
Date: Wed, 01 Oct 2014 20:03:29 +0300 [thread overview]
Message-ID: <83d2abk9i6.fsf@gnu.org> (raw)
In-Reply-To: <542C31B8.1090201@gmx.at>
> Date: Wed, 01 Oct 2014 18:54:16 +0200
> From: martin rudalics <rudalics@gmx.at>
> CC: 18597@debbugs.gnu.org
>
> (gdb) frame 8
> #8 0x0102231f in pos_visible_p (w=0x5af05e8, charpos=2658812, x=0x82e2cc, y=0x82e2c8, rtop=0x82e2c4, rbot=0x82e2c0, rowh=0x82e2bc, vpos=0x82e2b8) at xdisp.c:1437
> 1437 start_display (&it, w, top);
> (gdb) p w->start
> $11 = {
> i = 24813235
> }
Then I must be missing something, since this code in pos_visible_p:
SET_TEXT_POS_FROM_MARKER (top, w->start);
/* Scrolling a minibuffer window via scroll bar when the echo area
shows long text sometimes resets the minibuffer contents behind
our backs. */
if (CHARPOS (top) > ZV)
SET_TEXT_POS (top, BEGV, BEGV_BYTE);
/* Compute exact mode line heights. */
if (WINDOW_WANTS_MODELINE_P (w))
w->mode_line_height
= display_mode_line (w, CURRENT_MODE_LINE_FACE_ID (w),
BVAR (current_buffer, mode_line_format));
if (WINDOW_WANTS_HEADER_LINE_P (w))
w->header_line_height
= display_mode_line (w, HEADER_LINE_FACE_ID,
BVAR (current_buffer, header_line_format));
start_display (&it, w, top);
uses w->start for the position in 'top', with which it calls
start_display. And if somehow, the condition
if (CHARPOS (top) > ZV)
SET_TEXT_POS (top, BEGV, BEGV_BYTE);
fired, then still 'top' should be at BEGV. What am I missing here?
next prev parent reply other threads:[~2014-10-01 17:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-01 15:43 bug#18597: 25.0.50; Assertion violation in reseat_1 martin rudalics
2014-10-01 16:00 ` Eli Zaretskii
2014-10-01 16:05 ` martin rudalics
2014-10-01 16:41 ` Eli Zaretskii
2014-10-01 16:45 ` Eli Zaretskii
2014-10-01 16:54 ` martin rudalics
2014-10-01 17:03 ` Eli Zaretskii [this message]
2014-10-01 17:19 ` martin rudalics
2014-10-01 17:29 ` Eli Zaretskii
2014-10-01 17:40 ` martin rudalics
2014-12-25 10:55 ` martin rudalics
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=83d2abk9i6.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=18597@debbugs.gnu.org \
--cc=rudalics@gmx.at \
/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).