[64bit] emacs-w32 crash

Ken Brown kbrown@cornell.edu
Fri Apr 5 13:29:00 GMT 2013

Now that emacs-nox seems to be working OK, I'm beginning to test emacs-w32 and emacs-X11 (not yet uploaded to the 64-bit release).  emacs-w32 crashed overnight with the following stackdump:

Stack trace:
Frame        Function    Args
00000223740  0018006E4ED (000002236B8, 000DF0DF046, 00000000000, 00000000000)
00000223740  0018006F9CD (00000000000, 00000000000, 00000000358, 00000000000)
000002238B0  001801181D8 (000002239F0, 000002239F0, 0010053D66C, 00000223B20)
000000000C1  0018011572E (00000000000, 00000000000, 00000000000, 00000000000)
00000223C60  00180115BFB (00000000002, 00000223C58, 00180139E88, 0000000000B)
00000223C60  00180115DCC (00000223C58, 00000000000, 001005625F8, 00000000000)
00000223C60  00180111830 (00000000000, 001005625F8, 00000000000, 00000000400)
00000223C60  00100000002 (001005625F8, 00000000000, 00000000400, 00000223C90)
00000223C60  00000223C58 (001005625F8, 00000000000, 00000000400, 00000223C90)
End of stack trace

Running the top 7 function addresses through addr2line gives


I don't know if there's anything you can do with this information, and I'm not asking for debugging help at this early stage.  But I just thought I'd pass it along in case it points to a Cygwin bug.


More information about the Cygwin-developers mailing list