bug#15064: 24.3.50; emacs_backtrace.txt

bug#15064: 24.3.50; emacs_backtrace.txt

[Drew Adams]

FWIW: This time, the crash occurred (i.e., the fatal error dialog box
from Windows was displayed) when I did this:

I was using a different Emacs version (20).  I simply moved the mouse
over a frame of the development Emacs version (24).  IOW, I didn't even
touch the frame of the Emacs 24 version.  In principle, I was still
interacting with the Emacs 20 session.

At least that is what I think happened.  Very strange.  Maybe it means
something to you?


Backtrace:
0x011e71e4
0x011e7256
0x010da45c
0x0114f759
0x01004902
0x0105cca8
0x0106c8da
0x0106c9e5
0x0106d811
0x0106db0c
0x0106dcbd
0x011fad27
0x010e8685
0x010e8559
0x010eea4e
0x010e109f
0x010ed056
0x010de278
0x01169bb8
0x010ddbb6
0x011694d2
0x010ddb6e
0x010dd325
0x010dd4e1
0x010db7af
0x010010f9
0x774633a6
0x77dd9eee
0x77dd9ec1




In GNU Emacs 24.3.50.1 (i686-pc-mingw32)
 of 2013-08-07 on ODIEONE
Bzr revision: 113750 lekktu@gmail.com-20130808011911-0jzpc9xuncegg6x9
Windowing system distributor `Microsoft Corp.', version 6.1.7601
Configured using:
 `configure --prefix=/c/Devel/emacs/binary --enable-checking=yes,glyphs
 CFLAGS=-O0 -g3 LDFLAGS=-Lc:/Devel/emacs/lib
 CPPFLAGS=-Ic:/Devel/emacs/include'

bug#15064: 24.3.50; emacs_backtrace.txt

[Juanma Barranquero]

w32_backtrace at w32fns.c:7990
emacs_abort at w32fns.c:8022
terminate_due_to_signal at emacs.c:369
die at alloc.c:6558
matrix_row at dispnew.c:1452
draw_glyphs at xdisp.c:23853
expose_area at xdisp.c:28640
expose_line at xdisp.c:28665
expose_window at xdisp.c:28895
expose_window_tree at xdisp.c:28964
expose_frame at xdisp.c:29019
w32_read_socket at w32term.c:4386
gobble_input at keyboard.c:6827
get_input_pending at keyboard.c:6748
detect_input_pending_run_timers at keyboard.c:9893
read_char at keyboard.c:2804
read_key_sequence at keyboard.c:9056
command_loop_1 at keyboard.c:1434
internal_condition_case at eval.c:1339
command_loop_2 at keyboard.c:1161
internal_catch at eval.c:1113
command_loop at keyboard.c:1140
recursive_edit_1 at keyboard.c:779
Frecursive_edit at keyboard.c:843
main at emacs.c:1566
?? at crt1.c:0

bug#15064: 24.3.50; emacs_backtrace.txt

[Eli Zaretskii]

> Date: Fri, 9 Aug 2013 11:44:48 -0700 (PDT)
> From: Drew Adams <drew.adams@oracle.com>
> 
> I was using a different Emacs version (20).  I simply moved the mouse
> over a frame of the development Emacs version (24).  IOW, I didn't even
> touch the frame of the Emacs 24 version.  In principle, I was still
> interacting with the Emacs 20 session.

When mouse enters the Emacs frame, Emacs gets a message from Windows,
and processes it.

> At least that is what I think happened.  Very strange.  Maybe it means
> something to you?

It's an assertion violation.

bug#15064: 24.3.50; emacs_backtrace.txt

[Eli Zaretskii]

> From: Juanma Barranquero <lekktu@gmail.com>
> Date: Fri, 9 Aug 2013 22:44:47 +0200
> Cc: 15064@debbugs.gnu.org
> 
> w32_backtrace at w32fns.c:7990
> emacs_abort at w32fns.c:8022
> terminate_due_to_signal at emacs.c:369
> die at alloc.c:6558
> matrix_row at dispnew.c:1452
> draw_glyphs at xdisp.c:23853
> expose_area at xdisp.c:28640

Thanks.  I have no idea how could the mouse face coordinates be
outside valid limits here, but I think I worked around the problem in
trunk revision 113778.