From: Filipp Gunbin <fgunbin@fastmail.fm>
To: Ken Brown <kbrown@cornell.edu>
Cc: cygwin@cygwin.com
Subject: Re: crash on latest cygwin snapshot
Date: Thu, 02 Aug 2012 17:28:00 -0000 [thread overview]
Message-ID: <86sjc5b6me.fsf@w2139spb.ru.yotateam.com> (raw)
In-Reply-To: <501A946A.2030102@cornell.edu> (message from Ken Brown on Thu, 02 Aug 2012 10:53:30 -0400)
Ken Brown writes:
...
> Unfortunately, I'm finding that emacs is unstable: The emacs window
> (running under X) simply disappears after 12-24 hours. This may not
> have anything to do with the most recent changes. I haven't yet tested
> any earlier snapshots.
...
Hi Ken,
I observe Emacs crashes in the following scenario:
- emacs -nw
- run cygwin setup utility, click through it until it finishes (it does not matter whether
any packages are installed or not)
- continue with emacs (for example, type "C-x C-f C-g") - it will crash
I don't know if it is related to the problem in this discussion, and
probably it's not a good idea to update Cygwin while running Cygwin programs,
but maybe it will give some hint.
I'm currently on Cygwin 1.7.16, Windows 7 (maybe it started after I
upgraded from Vista recently, but I'm not sure).
--
Filipp Gunbin
--
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 prev parent reply other threads:[~2012-08-02 16:29 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-24 21:30 marco atzeri
2012-06-25 4:31 ` Christopher Faylor
2012-06-25 7:35 ` marco atzeri
2012-06-25 8:07 ` Corinna Vinschen
2012-06-25 8:38 ` marco atzeri
2012-06-25 9:02 ` Corinna Vinschen
2012-06-25 9:36 ` marco atzeri
2012-06-25 11:58 ` marco atzeri
2012-06-25 14:46 ` Christopher Faylor
2012-06-25 15:01 ` marco atzeri
2012-06-25 15:29 ` Christopher Faylor
2012-06-25 16:28 ` marco atzeri
2012-06-26 11:53 ` Ken Brown
2012-06-26 14:10 ` Christopher Faylor
2012-06-26 15:04 ` Christopher Faylor
2012-06-26 15:32 ` Corinna Vinschen
2012-06-26 15:52 ` Christopher Faylor
2012-06-26 16:32 ` Achim Gratz
2012-06-26 18:51 ` marco atzeri
2012-06-26 19:24 ` Christopher Faylor
2012-06-26 19:46 ` marco atzeri
2012-06-26 19:48 ` Christopher Faylor
2012-06-26 19:55 ` marco atzeri
2012-06-26 20:15 ` Christopher Faylor
2012-06-26 20:28 ` marco atzeri
2012-06-26 20:32 ` Christopher Faylor
2012-06-26 20:51 ` marco atzeri
2012-06-26 20:53 ` Christopher Faylor
2012-06-27 1:47 ` Christopher Faylor
2012-07-02 14:43 ` marco atzeri
2012-08-01 9:43 ` Corinna Vinschen
2012-08-01 10:35 ` marco atzeri
2012-08-01 12:29 ` Corinna Vinschen
2012-08-01 12:42 ` marco atzeri
2012-08-01 12:46 ` Corinna Vinschen
2012-08-01 12:52 ` marco atzeri
2012-08-01 12:58 ` Corinna Vinschen
2012-08-01 12:46 ` Ken Brown
2012-08-01 12:59 ` Corinna Vinschen
2012-08-02 15:57 ` Ken Brown
2012-08-02 16:29 ` Corinna Vinschen
2012-08-02 17:28 ` Filipp Gunbin [this message]
2012-08-02 18:15 ` Ken Brown
2012-08-03 7:43 ` Filipp Gunbin
2012-08-02 18:21 ` Achim Gratz
2012-08-02 18:40 ` Christopher Faylor
2012-08-02 19:29 ` Achim Gratz
2012-08-02 19:42 ` Christopher Faylor
2012-08-03 3:41 ` Ken Brown
2012-08-03 7:05 ` Christopher Faylor
2012-08-03 7:49 ` Achim Gratz
2012-08-03 16:24 ` Christopher Faylor
2012-08-03 20:45 ` Ken Brown
2012-08-04 2:14 ` Christopher Faylor
2012-08-05 4:39 ` 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=86sjc5b6me.fsf@w2139spb.ru.yotateam.com \
--to=fgunbin@fastmail.fm \
--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).