From: Zdzislaw Meglicki <zdzisiekm@sbcglobal.net>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>,
"kbrown@cornell.edu" <kbrown@cornell.edu>
Subject: Emacs-w32... still crashing
Date: Tue, 03 Jun 2014 22:03:00 -0000 [thread overview]
Message-ID: <1401832858.77832.YahooMailNeo@web185401.mail.gq1.yahoo.com> (raw)
And... another crash. I didn't run it under gdb this
time and it didn't dump anything either, but I got
interesting new message I didn't see before:
*** fatal error - WFSO failed waiting for timer thread, Win32 error 0
Interesting? Perhaps all these crashes have something to
do with the timer?
Zdzislaw (Gustav) Meglicki
Indiana University
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next reply other threads:[~2014-06-03 22:03 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-03 22:03 Zdzislaw Meglicki [this message]
2014-06-05 19:05 ` Ken Brown
2014-06-05 19:51 ` Christopher Faylor
2014-06-05 20:09 ` Ken Brown
2014-06-06 7:53 ` Csaba Raduly
-- strict thread matches above, loose matches on Subject: below --
2014-07-07 19:15 Emacs-w32... Still Crashing Zdzislaw Meglicki
2014-07-08 13:56 ` Ken Brown
2014-07-08 15:02 ` Christopher Faylor
2014-07-08 16:36 ` Yaakov Selkowitz
2014-07-08 16:44 ` Christopher Faylor
2014-07-09 10:27 ` Corinna Vinschen
2014-07-09 10:42 ` Corinna Vinschen
2014-07-09 10:15 ` Corinna Vinschen
2014-07-09 12:22 ` Corinna Vinschen
2014-07-09 13:52 ` Ken Brown
2014-06-17 14:28 Emacs-w32... still crashing Zdzislaw Meglicki
2014-06-04 14:24 Zdzislaw Meglicki
2014-06-03 20:04 Zdzislaw Meglicki
2014-06-03 21:37 ` Larry Hall (Cygwin)
2014-06-04 12:46 ` Ken Brown
2014-06-03 18:00 Zdzislaw Meglicki
2014-05-21 22:55 Zdzislaw Meglicki
2014-05-22 1:11 ` Ken Brown
2014-05-19 14:42 Zdzislaw Meglicki
2014-05-19 21:13 ` Ken Brown
2014-05-21 19:14 ` Ken Brown
2014-05-14 22:31 Zdzislaw Meglicki
2014-05-15 0:07 ` Ken Brown
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1401832858.77832.YahooMailNeo@web185401.mail.gq1.yahoo.com \
--to=zdzisiekm@sbcglobal.net \
--cc=cygwin@cygwin.com \
--cc=kbrown@cornell.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).