bug#24614: 25.1.50; Exception after moving mouse over over a different window

[Alain Schneble]

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Alain Schneble <a.s@realize.ch>
>> CC: <24614@debbugs.gnu.org>
>> Date: Tue, 4 Oct 2016 17:54:33 +0200
>> 
>> > Is this GDB session still alive?
>> 
>> Thanks for looking into it.  Yes, GDB session is still alive.
>
> OK, so what does this print:
>
>  (gdb) frame 10
>  (gdb) p *glyph
>
> also these:
>
>  (gdb) p *width
>  (gdb) p w->contents
>  (gdb) xtype
>
> If the last command says it's a buffer, type "xbuffer", otherwise type
> "xwindow" and show the result.

(gdb) frame 10
#10 0x00000004000469f9 in get_window_cursor_type (active_cursor=<synthetic 
pointer>, width=0xbfd6ac, glyph=0x10c46fd0, w=0x12af8400) at xdisp.c:28096
28096         if (glyph != NULL && glyph->type == XWIDGET_GLYPH)
(gdb) p *width
$3 = 1
(gdb) p w->contents
$4 = 282715685
(gdb) xtype
Lisp_Vectorlike
PVEC_BUFFER
(gdb) xbuffer
$5 = (struct buffer *) 0x10d9e620
(unsigned char *) 0xc661598 "TaskList.org"

> Btw, how come the call to get_window_cursor_type is shown with its
> argument in reverse order?  In the backtrace:

I have no clue... Could optimization reorder the arguments?

>
>   #10 0x00000004000469f9 in get_window_cursor_type (active_cursor=<synthetic 
> pointer>, width=0xbfd6ac, glyph=0x10c46fd0, w=0x12af8400) at xdisp.c:28096
>
> when the actual function argument list is this:
>
>   get_window_cursor_type (struct window *w, struct glyph *glyph, int *width,
>                           bool *active_cursor)
>
> What does this print:
>
>  (gdb) ptype get_window_cursor_type

(gdb) ptype get_window_cursor_type
type = enum text_cursor_kinds {DEFAULT_CURSOR = -2, NO_CURSOR, 
FILLED_BOX_CURSOR, HOLLOW_BOX_CURSOR, BAR_CURSOR, HBAR_CURSOR} (_Bool *, int *, 
struct glyph *, struct window *)

> Something really weird went on in that frame #10...

Should I have fear of something now? ;)

Thanks,
Alain