From: Eli Zaretskii <eliz@gnu.org>
To: sds@gnu.org, Martin Rudalics <rudalics@gmx.at>
Cc: 12251@debbugs.gnu.org
Subject: bug#12251: 24.2.50; crash in note_mouse_highlight
Date: Wed, 22 Aug 2012 20:09:31 +0300 [thread overview]
Message-ID: <83vcgaam5w.fsf@gnu.org> (raw)
In-Reply-To: <87sjbfhcii.fsf@gnu.org>
> From: Sam Steingold <sds@gnu.org>
> Cc: 12251@debbugs.gnu.org
> Date: Tue, 21 Aug 2012 22:43:49 -0400
>
> #8 0x00000000004f5da5 in cmd_error_internal (data=68832822, context=0x7fffffffcf30 "") at /home/sds/src/emacs/trunk/src/keyboard.c:1147
> 1147 bitch_at_user ();
> (gdb) p data
> $1 = 68832822
> (gdb) xtype
> Lisp_Cons
> (gdb) xcons
> $2 = (struct Lisp_Cons *) 0x41a4e30
> {
> car = 0xb7c612,
> u = {
> cdr = 0x41a4e56,
> chain = 0x41a4e56
> }
> }
> (gdb) p 0xb7c612
> $3 = 12043794
> (gdb) xtype
> Lisp_Symbol
> (gdb) xsymbol
> $4 = (struct Lisp_Symbol *) 0xb7c610
> "error"
> (gdb) p 0x41a4e56
> $5 = 68832854
> (gdb) xtype
> Lisp_Cons
> (gdb) xcons
> $6 = (struct Lisp_Cons *) 0x41a4e50
> {
> car = 0x3032031,
> u = {
> cdr = 0xb6fbd2,
> chain = 0xb6fbd2
> }
> }
> (gdb) p 0x3032031
> $7 = 50536497
> (gdb) xtype
> Lisp_String
> (gdb) xstring
> $8 = (struct Lisp_String *) 0x3032030
> "#<window 139> is not a valid window"
> (gdb) p 0xb6fbd2
> $9 = 11992018
> (gdb) xtype
> Lisp_Symbol
> (gdb) xsymbol
> $10 = (struct Lisp_Symbol *) 0xb6fbd0
> "nil"
> (gdb)
Martin, could this be due to your changes in revision 109644?
Sam, if you revert that commit, does the problem go away?
Anyway, I think the crash with a mouse is not the root cause here. We
are somehow hitting a dead window, and then trying to activate mouse
highlight on that window.
next prev parent reply other threads:[~2012-08-22 17:09 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 [this message]
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
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=83vcgaam5w.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).