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

[Alain Schneble]

Eli Zaretskii <eliz@gnu.org> writes:

> What about
>
>  (gdb) p *glyph
>

(gdb) p *glyph
Cannot access memory at address 0x10c46fd0

(Not a valid excuse for having missed that one, but sorry, I was in a
hurry.  I had to leave the train.)

>> > 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?
>
> Maybe the function was inlined.  Or maybe it's a GDB bug.

Aha.

>> > Something really weird went on in that frame #10...
>> 
>> Should I have fear of something now? ;)
>
> Fear of a crash, of course.

I'll resist.

> If this happens again, I suggest to build an unoptimized binary and
> see if the problem can be reproduced there.

Ok, I'll watch out and will try to catch it with an unoptimized build if
that happens again.

Thanks,
Alain