From: Sam Steingold <sds@gnu.org>
To: martin rudalics <rudalics@gmx.at>
Cc: 12251@debbugs.gnu.org
Subject: bug#12251: 24.2.50; crash in note_mouse_highlight
Date: Mon, 27 Aug 2012 15:01:55 -0400 [thread overview]
Message-ID: <87wr0k17mk.fsf@gnu.org> (raw)
In-Reply-To: <5038D5BF.70306@gmx.at> (martin rudalics's message of "Sat, 25 Aug 2012 15:40:15 +0200")
> * martin rudalics <ehqnyvpf@tzk.ng> [2012-08-25 15:40:15 +0200]:
>
>> tried, but got a crash in different place instead.
>
> Interesting. Could you try the more invasive patch I attached? I
> have no idea what it could break, so please don't do any important
> work with it.
I rebuilt bzr tip this morning and now I am getting this:
Debugger entered--Lisp error: (error "#<window 3> is not a live window")
signal(error ("#<window 3> is not a live window"))
error("%s is not a live window" #<window 3>)
window-normalize-window(#<window 3> t)
record-window-buffer(#<window 3>)
set-window-configuration(#<window-configuration>)
sds-window-configuration-restore()
run-hooks(gnus-suspend-gnus-hook)
apply(run-hooks gnus-suspend-gnus-hook)
gnus-run-hooks(gnus-suspend-gnus-hook)
gnus-group-suspend()
call-interactively(gnus-group-suspend nil nil)
when exiting or suspending gnus and
--
Sam Steingold (http://sds.podval.org/) on Ubuntu 12.04 (precise) X 11.0.11103000
http://www.childpsy.net/ http://pmw.org.il http://www.memritv.org
http://thereligionofpeace.com http://camera.org http://iris.org.il
Money does not bother me at all. In fact, it calms me down.
next prev parent reply other threads:[~2012-08-27 19:01 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 [this message]
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
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=87wr0k17mk.fsf@gnu.org \
--to=sds@gnu.org \
--cc=12251@debbugs.gnu.org \
--cc=rudalics@gmx.at \
/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).