From: Tassilo Horn <tsdh@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 12814@debbugs.gnu.org
Subject: bug#12814: 24.3.50; Emacs crash in event_to_kboard at keyboard.c:3421
Date: Tue, 06 Nov 2012 21:01:26 +0100 [thread overview]
Message-ID: <87y5ie33hl.fsf@thinkpad.tsdh.de> (raw)
In-Reply-To: <83a9uu35x4.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 06 Nov 2012 21:08:55 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
>> Um, it's an integer (which is also visible in the other backtraces).
>>
>> Program received signal SIGSEGV, Segmentation fault.
>> 0x0000000000543714 in event_to_kboard (event=0xbd2ba0 <kbd_buffer+98112>)
>> at keyboard.c:3421
>> 3421 if (WINDOWP (obj))
>> (gdb) p obj
>> $1 = 1666821
>
> All Lisp objects look like integers, but aren't. What does "xtype"
> say about it? Like this:
>
> (gdb) p obj
> (gdb) xtype
Program received signal SIGSEGV, Segmentation fault.
0x0000000000543714 in event_to_kboard (event=0xbe01e0 <kbd_buffer+152960>)
at keyboard.c:3421
3421 if (WINDOWP (obj))
(gdb) p obj
$1 = 7816245
(gdb) xtype
No symbol "GCTYPEBITS" in current context.
Bye,
Tassilo
next prev parent reply other threads:[~2012-11-06 20:01 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-06 10:56 bug#12814: 24.3.50; Emacs crash in event_to_kboard at keyboard.c:3421 Tassilo Horn
2012-11-06 15:13 ` Tassilo Horn
2012-11-06 16:16 ` Eli Zaretskii
2012-11-06 18:11 ` Tassilo Horn
2012-11-06 18:27 ` Tassilo Horn
2012-11-06 19:08 ` Eli Zaretskii
2012-11-06 20:01 ` Tassilo Horn [this message]
2012-11-06 20:21 ` Eli Zaretskii
2012-11-06 20:50 ` Paul Eggert
2012-11-06 20:54 ` Tassilo Horn
2012-11-06 21:04 ` Paul Eggert
2012-11-06 21:20 ` Tassilo Horn
2012-11-06 21:29 ` Eli Zaretskii
2012-11-07 11:39 ` Tassilo Horn
2012-11-07 17:17 ` Eli Zaretskii
2012-11-07 18:45 ` Tassilo Horn
2012-11-07 19:19 ` Eli Zaretskii
2012-11-08 7:56 ` Tassilo Horn
2012-11-08 9:30 ` Dmitry Antipov
2012-11-08 10:55 ` Tassilo Horn
2012-11-12 7:34 ` Tassilo Horn
2012-11-06 21:27 ` 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=87y5ie33hl.fsf@thinkpad.tsdh.de \
--to=tsdh@gnu.org \
--cc=12814@debbugs.gnu.org \
--cc=eliz@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 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.