From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: 11969-done@debbugs.gnu.org
Subject: bug#11969: 24.1.50; crash on Windows
Date: Wed, 18 Jul 2012 21:02:16 +0300 [thread overview]
Message-ID: <83zk6x7xsn.fsf@gnu.org> (raw)
In-Reply-To: <D58D95A2005D4054B28D498F3292FAC2@us.oracle.com>
> From: "Drew Adams" <drew.adams@oracle.com>
> Date: Tue, 17 Jul 2012 17:28:27 -0700
>
> This is the backtrace. The session no longer exists. HTH. If not,
> feel free to close the bug.
Closed.
This is another one in the series of assertion violations that happen
only in your configuration. The problem is this:
> #2 0x01041c65 in die (
> msg=0x15ab394 "assertion failed: EQ (XFRAME (selected_frame)->selected_window, selected_window)", file=0x15a25b8 "xdisp.c", line=13446) at alloc.c:6639
IOW, the selected window of the selected frame is not the window
stored in the variable selected_window, which is what redisplay
expects.
My guess is that this is somehow related to your massive use of pop-up
frames. Something happens there that causes this mismatch. But what
exactly is a problem is hard to say without knowing at least the
values of the two windows involved in the test. Are both of them
windows, or is one of them nil or something like that? If the former,
which window is each one of them, and how are they related to whatever
you were doing at the moment of the crash? Etc. et. -- you _must_
understand that unless you help us dig into this mystery, this bug
will probably _never_ be fixed. And since you need guidance to use
the debugger on the C level, the only way of digging is if you leave
the crashed session running under the debugger and let us ask you for
information.
It's your call.
next prev parent reply other threads:[~2012-07-18 18:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-18 0:28 bug#11969: 24.1.50; crash on Windows Drew Adams
2012-07-18 18:02 ` Eli Zaretskii [this message]
2012-07-19 8:24 ` Stefan Monnier
2012-07-19 15:23 ` 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=83zk6x7xsn.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=11969-done@debbugs.gnu.org \
--cc=drew.adams@oracle.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 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.