From: Eli Zaretskii <eliz@gnu.org>
To: martin rudalics <rudalics@gmx.at>
Cc: sds@gnu.org, 12251@debbugs.gnu.org
Subject: bug#12251: 24.2.50; crash in note_mouse_highlight
Date: Thu, 23 Aug 2012 21:43:20 +0300 [thread overview]
Message-ID: <836289a1pz.fsf@gnu.org> (raw)
In-Reply-To: <50366607.7090209@gmx.at>
> Date: Thu, 23 Aug 2012 19:19:03 +0200
> From: martin rudalics <rudalics@gmx.at>
> CC: sds@gnu.org, 12251@debbugs.gnu.org
>
> >> >> "#<window 139> is not a valid window"
> >>
> >> The above means that we've been running Lisp code on a dead window and
> >> that call was rejected with an error by `window-normalize-window'. If
> >> this happens during a call from C, we have a problem.
> >
> > I don't think this error was thrown from C.
>
> The error was obviously thrown from Lisp which per se is harmless. But
> I'm quite convinced that it was thrown by a Lisp function directly or
> indirectly called from C.
Why do you think that?
> > Most probably, it was
> > thrown from Lisp, but since that unwinds the stack, there's no Lisp
> > backtrace that could confirm that.
>
> How could we explain a crash if it's all within Lisp code?
It's not within Lisp anymore; the error throws to top-level, and Emacs
tries to read input, at which time it gets a mouse event.
> > I guess we need more checks in the mouse-highlight code, to account
> > for such cases.
>
> Is note_mouse_highlight all we have to look at?
Who knows? But if there are more, we will get more crashes ;-)
next prev parent reply other threads:[~2012-08-23 18:43 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-21 18:20 bug#12251: 24.2.50; crash in note_mouse_highlight Sam Steingold
2012-08-21 18:42 ` Eli Zaretskii
2012-08-21 19:02 ` Sam Steingold
2012-08-21 19:22 ` Eli Zaretskii
2012-08-22 2:43 ` Sam Steingold
2012-08-22 17:09 ` Eli Zaretskii
2012-08-22 17:29 ` Sam Steingold
2012-08-22 21:12 ` Sam Steingold
2012-08-23 8:48 ` martin rudalics
2012-08-23 13:19 ` Sam Steingold
2012-08-23 17:18 ` martin rudalics
2012-08-24 20:33 ` Sam Steingold
2012-08-25 13:40 ` martin rudalics
2012-08-27 19:01 ` Sam Steingold
2012-08-27 19:05 ` Sam Steingold
2012-08-27 21:10 ` martin rudalics
2012-08-28 16:35 ` Sam Steingold
2012-08-28 17:05 ` martin rudalics
2012-08-29 9:34 ` martin rudalics
2012-08-29 14:42 ` Sam Steingold
2012-08-30 8:03 ` martin rudalics
2012-08-30 11:02 ` Sam Steingold
2012-09-01 9:36 ` Eli Zaretskii
2012-09-05 19:56 ` Sam Steingold
2012-09-06 2:31 ` Sam Steingold
2012-09-06 3:13 ` Sam Steingold
2012-09-06 5:15 ` Werner LEMBERG
2012-09-06 5:04 ` Eli Zaretskii
2012-09-06 7:20 ` martin rudalics
2012-09-06 7:32 ` martin rudalics
2012-08-30 12:39 ` Sam Steingold
2012-08-30 12:49 ` martin rudalics
2012-09-01 9:40 ` Eli Zaretskii
2012-08-23 16:20 ` Eli Zaretskii
2012-08-23 17:19 ` martin rudalics
2012-08-23 18:43 ` Eli Zaretskii [this message]
2012-08-24 9:44 ` 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=836289a1pz.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=12251@debbugs.gnu.org \
--cc=rudalics@gmx.at \
--cc=sds@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).