GNU bug report logs - #12251
24.2.50; crash in note_mouse_highlight

Previous Next

Package: emacs;

Reported by: sds <at> gnu.org

Date: Tue, 21 Aug 2012 18:22:01 UTC

Severity: normal

Found in version 24.2.50

Done: Glenn Morris <rgm <at> gnu.org>

Bug is archived. No further changes may be made.

Full log


Message #47 received at 12251 <at> debbugs.gnu.org (full text, mbox):

From: martin rudalics <rudalics <at> gmx.at>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: sds <at> gnu.org, 12251 <at> debbugs.gnu.org
Subject: Re: bug#12251: 24.2.50; crash in note_mouse_highlight
Date: Fri, 24 Aug 2012 11:44:57 +0200
>> 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?

An error with code attempting to operate on a dead window within
"normal" Lisp is a strange case.  It can be due to users leaving a
dangling reference to such a window somewhere in their code but I doubt
that many people do that.  And when such an error happens, there is no
reason why it should expand into a crash.  The (implicit) invariants of
a window tree should not be violated by Elisp code.

OTOH, calling an Elisp function from C in a state where the window tree
invariants are temporarily violated can easily lead to a crash.

>> 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.

That would be a _very_ strange coinicidence.

martin




This bug report was last modified 12 years and 156 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.