Re: assertion failed: c == event->code

[Jason Rumney <jasonr@gnu.org>]

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.