From: Jason Rumney <jasonr@gnu.org>
To: Juanma Barranquero <lekktu@gmail.com>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>,
Emacs-Devel <emacs-devel@gnu.org>
Subject: Re: assertion failed: c == event->code
Date: Fri, 14 Dec 2007 09:24:15 +0000 [thread overview]
Message-ID: <47624BBF.4000602@gnu.org> (raw)
In-Reply-To: <f7ccd24b0712130844x368681ecsfcc8b18e852d29df@mail.gmail.com>
Juanma Barranquero wrote:
> On Dec 13, 2007 5:37 PM, Jason Rumney <jasonr@gnu.org> wrote:
>
> I can try to debug it, if you explain to me what to look for and where.
>
If you reproduce the bug, you get this backtrace:
keyboard.c:5548: Emacs fatal error: assertion failed: c == event->code
Breakpoint 1, w32_abort () at w32fns.c:9127
9127 button = MessageBox (NULL,
(gdb) bt
#0 w32_abort () at w32fns.c:9127
#1 0x0101f2fb in die (msg=0x13598f8 "assertion failed: c == event->code",
file=0x135686a "keyboard.c", line=5548) at alloc.c:6287
#2 0x01091bfc in read_char (commandflag=1, nmaps=2, maps=0x82fb70,
prev_event=25171969, used_mouse_menu=0x82fc18, end_time=0x0)
at keyboard.c:5548
#3 0x010928d1 in read_key_sequence (keybuf=0x82fce4, bufsize=30,
prompt=25171969, dont_downcase_last=0, can_return_switch_frame=1,
fix_current_buffer=1) at keyboard.c:9459
"frame 2" takes you to the point in keyboard.c where the assertion was triggered.
"print c", "print event->code" will print the values of the respective variables.
From there, you can go further up the stack and print other related variables to see where event->code became greater than 0xff.
next prev parent reply other threads:[~2007-12-14 9:24 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-12 15:14 assertion failed: c == event->code Juanma Barranquero
2007-12-12 17:30 ` Stefan Monnier
2007-12-12 18:00 ` Juanma Barranquero
2007-12-12 20:05 ` Stefan Monnier
2007-12-12 22:54 ` Juanma Barranquero
2007-12-12 23:41 ` Jason Rumney
2007-12-13 14:16 ` Jason Rumney
2007-12-13 15:09 ` Juanma Barranquero
2007-12-13 16:37 ` Jason Rumney
2007-12-13 16:44 ` Juanma Barranquero
2007-12-14 9:24 ` Jason Rumney [this message]
2007-12-14 10:11 ` Juanma Barranquero
2007-12-14 1:08 ` Kenichi Handa
2007-12-14 8:47 ` Jason Rumney
2007-12-14 11:11 ` Kenichi Handa
2007-12-14 12:23 ` Jason Rumney
2007-12-14 14:25 ` Juanma Barranquero
2007-12-16 15:19 ` Juanma Barranquero
2007-12-16 20:49 ` Jason Rumney
2007-12-16 20:53 ` Juanma Barranquero
2007-12-16 20:59 ` Juanma Barranquero
2007-12-16 21:25 ` Miles Bader
2007-12-17 1:52 ` Jason Rumney
2007-12-17 9:06 ` Juanma Barranquero
2007-12-12 18:36 ` Andreas Schwab
2007-12-12 17:54 ` 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=47624BBF.4000602@gnu.org \
--to=jasonr@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=lekktu@gmail.com \
--cc=monnier@iro.umontreal.ca \
/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).