From: Ken Raeburn <raeburn@permabit.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 23013@debbugs.gnu.org
Subject: bug#23013: 25.0.92; assertion failure on marker outside text range in echo area
Date: Thu, 7 Apr 2016 18:32:51 -0400 [thread overview]
Message-ID: <CAJJWxE-Dh1FOsmK++1B8Y6vDQPnfw3d4_R8dn1q3DTkB=Hg10g@mail.gmail.com> (raw)
In-Reply-To: <838u1h9gq1.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1677 bytes --]
On Thu, Mar 17, 2016 at 1:06 PM, Eli Zaretskii <eliz@gnu.org> wrote:
> I've reviewed the changes between 25.0.90 and 25.0.92. I see nothing
> that could be directly linked to this problem. The only commits that
> might be even remotely related are these 3:
>
> d82f24ba8530eb8de04a319cc80742a0a953040e
>
This could be interesting...
> 84829495b5746417f5eaf9be693fb35f0509697a
>
scroll-conservatively is 0, at least in the core file, and it looks like
the only mode I use that changes it is jabber-chat-mode which sets it to 5,
so either way it shouldn't reach the path where this change occurred.
> 06a872b71d6580e0699600844bb9526602437990
>
Probably not relevant as I was only using X frames. There's the initial
frame created in daemon mode, which has FRAME_VISIBLE_P true but
FRAME_GARBAGED_P false (also FRAME_TERMCAP_P and FRAME_MSDOS_P false) so it
wouldn't follow that path.
>
> Maybe you should try reverting these one by one.
>
I have no reliable way of reproducing the problem, so not hitting another
crash once a change is reverted wouldn't tell me much. Is there something
further I could introduce a check for to see if one of these patches might
be causing the problem?
>
> It could also happen that the assertions you saw in 25.0.90 are caused
> by the same problem that now causes this bug. Any idea if those
> assertions were for the mini-window as well?
>
Both assertions in .90 were in find_last_row_displaying_text, checking
row->enabled_p. The window being examined (next frame up, try_window_id) is
the root window of its frame. Redisplay is being done during a call to
wait_reading_process_output. So it doesn't look very similar.
[-- Attachment #2: Type: text/html, Size: 2656 bytes --]
next prev parent reply other threads:[~2016-04-07 22:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-14 19:55 bug#23013: 25.0.92; assertion failure on marker outside text range in echo area Ken Raeburn
2016-03-15 19:00 ` Ken Raeburn
2016-03-15 19:14 ` Eli Zaretskii
2016-03-15 19:46 ` Ken Raeburn
2016-03-15 20:13 ` Eli Zaretskii
2016-03-15 21:16 ` Ken Raeburn
2016-03-16 15:32 ` Eli Zaretskii
2016-03-16 19:28 ` Ken Raeburn
2016-03-17 17:06 ` Eli Zaretskii
2016-04-07 22:32 ` Ken Raeburn [this message]
2016-04-08 7:38 ` Eli Zaretskii
2016-04-22 21:01 ` Ken Raeburn
2016-04-23 7:55 ` Eli Zaretskii
2020-08-12 3:33 ` Stefan Kangas
2020-09-14 21:23 ` Ken Raeburn
2020-09-15 7:35 ` Stefan Kangas
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='CAJJWxE-Dh1FOsmK++1B8Y6vDQPnfw3d4_R8dn1q3DTkB=Hg10g@mail.gmail.com' \
--to=raeburn@permabit.com \
--cc=23013@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.