unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Dmitry Antipov <dmantipov@yandex.ru>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 13007@debbugs.gnu.org
Subject: bug#13007: 24.3.50; emacs_backtrace.txt
Date: Tue, 27 Nov 2012 20:49:44 +0400	[thread overview]
Message-ID: <50B4EF28.6040905@yandex.ru> (raw)
In-Reply-To: <83k3t7xemd.fsf@gnu.org>

On 11/27/2012 07:14 PM, Eli Zaretskii wrote:

> The crash is due to assertion violation here:
>
>    static int
>    window_outdated (struct window *w)
>    {
>      eassert (XBUFFER (w->buffer) == current_buffer);  <<<<<<<<<<<<<<<<<<
>      return (w->last_modified < MODIFF
> 	    || w->last_overlay_modified < OVERLAY_MODIFF);
>    }
>
> Dmitry, why did you add this assertion?  What code that you introduced
> assumes that this condition is always true?

This eassert was installed just to trap on the suspicious use cases as we found
in this bug :-).

> I suspect that we need to change this assertion to
>
>      eassert (MINI_WINDOW_P (w) || w->pseudo_window_p
>               || XBUFFER (w->buffer) == current_buffer);
>
> At least in this case (see the backtrace below), window_outdated is
> called from code that handles minibuffer windows, so I'm guessing the
> above assertion is not true.

Hm... this really helps to bypass eassert, but:

1) is it meaningful to compare w->last_modified of minibuffer window with
MODIFF? Shouldn't we compare it against BUFF_MODIFF of appropriate minibuffer?

2) is it possible to have an overlay in a minibuffer?

3) should window_outdated_p be applicable to pseudowindows at all?

Dmitry






  reply	other threads:[~2012-11-27 16:49 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-27  6:23 bug#13007: 24.3.50; emacs_backtrace.txt Drew Adams
2012-11-27  6:28 ` Drew Adams
2012-11-27 15:15   ` Eli Zaretskii
2012-11-27 15:41     ` Drew Adams
2012-11-27 15:44       ` Drew Adams
2012-11-27 16:39     ` Juanma Barranquero
2012-11-27 18:02       ` Eli Zaretskii
2012-11-27 15:14 ` Eli Zaretskii
2012-11-27 16:49   ` Dmitry Antipov [this message]
2012-11-27 17:47     ` Eli Zaretskii
2012-11-27 17:58       ` Jambunathan K
2012-11-27 18:10         ` Drew Adams
2012-11-28  7:19       ` Dmitry Antipov
2012-11-28 13:09         ` Juanma Barranquero
2012-11-28 15:51           ` Dmitry Antipov
2012-11-28 17:59             ` Eli Zaretskii
2012-11-29  6:19               ` Dmitry Antipov
2012-11-29 16:46                 ` Eli Zaretskii
2012-11-29 17:02                   ` Drew Adams
2012-11-29 17:39                     ` Eli Zaretskii
2012-11-29 17:47                       ` Drew Adams
2012-11-29 18:08                         ` Eli Zaretskii
2012-11-29 18:13                           ` Drew Adams
2012-11-29 19:50                             ` Eli Zaretskii
2012-11-29 17:23                   ` Dmitry Antipov
2012-11-30  9:53                     ` Eli Zaretskii
2012-11-30 15:50                       ` Dmitry Antipov
2012-11-30 16:59                         ` Eli Zaretskii
2015-12-29 11:08                       ` Lars Ingebrigtsen
2015-12-29 17:37                         ` Eli Zaretskii
2016-01-02 11:10                           ` Eli Zaretskii
2012-11-29 19:14                   ` Stefan Monnier
2012-11-29 19:54                     ` 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

  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=50B4EF28.6040905@yandex.ru \
    --to=dmantipov@yandex.ru \
    --cc=13007@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 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).