Eli Zaretskii <eliz@gnu.org> writes:

> They haven't, but now you should be able to use xtype to see what kind
> of object is obj that cases the crash.

Ok.  It took much longer for the crash to occur, but now xtype worked
(complete backtrace attached).

Program received signal SIGSEGV, Segmentation fault.
0x00000000005437a4 in event_to_kboard (event=0xbc0660 <kbd_buffer+18944>)
    at keyboard.c:3421
3421	  if (WINDOWP (obj))
(gdb) p obj
$1 = 7652357
(gdb) xtype 
Lisp_Vectorlike
Cannot access memory at address 0x74c400

Bye,
Tassilo