unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Ken Raeburn <raeburn@permabit.com>
Cc: 23013@debbugs.gnu.org
Subject: bug#23013: 25.0.92; assertion failure on marker outside text range in echo area
Date: Thu, 17 Mar 2016 19:06:30 +0200	[thread overview]
Message-ID: <838u1h9gq1.fsf@gnu.org> (raw)
In-Reply-To: <CAJJWxE-hiU1SAHkRwd-FZ7f5RSkFKhsn5ffhp4EHCXhH6DYdwg@mail.gmail.com> (message from Ken Raeburn on Wed, 16 Mar 2016 15:28:08 -0400)

> Date: Wed, 16 Mar 2016 15:28:08 -0400
> From: Ken Raeburn <raeburn@permabit.com>
> Cc: 23013@debbugs.gnu.org
> 
>      Anyway, do you have any explanation for why this started happening
>     now?  Did you switch from an older Emacs version, or changed something
>     in your local system configuration or in the way you invoke Emacs?
>     (I'm trying to establish whether this is an old problem, or something
>     that was caused by recent changes.)
> 
> I switched one week ago to emacs-25.0.92 from emacs-25.0.90, which I'd been running since early or mid February.  I didn't see this problem in .90, though a couple of assertion failures in find_last_row_displaying_text prompted me to pick up the newer snapshot.  Some changes I saw in the log for .92 made me think maybe that had been addressed, so I wasn't planning to report the assertion failure unless I saw it again in the newer snapshot.

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
  84829495b5746417f5eaf9be693fb35f0509697a
  06a872b71d6580e0699600844bb9526602437990

Maybe you should try reverting these one by one.

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?





  reply	other threads:[~2016-03-17 17:06 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 [this message]
2016-04-07 22:32                 ` Ken Raeburn
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

  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=838u1h9gq1.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=23013@debbugs.gnu.org \
    --cc=raeburn@permabit.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).