From: Ken Brown <kbrown@cornell.edu>
To: cygwin@cygwin.com
Subject: Re: crash on latest cygwin snapshot
Date: Tue, 26 Jun 2012 11:53:00 -0000 [thread overview]
Message-ID: <4FE9A2A1.3040802@cornell.edu> (raw)
In-Reply-To: <4FE786DA.2050208@gmail.com>
On 6/24/2012 5:30 PM, marco atzeri wrote:
> while building latest atlas I hit a bug that is crashing all the running
> cygwin process.
> It crashes on 20120619 snapshot and also latest cvs source.
> No issue on 20120611 snapshot.
I'm also seeing this crash, but it does not kill all running cygwin
processes. The only processes that die are the mintty processes and the
associated bash processes. For example, it just happened a few minutes
ago, and XWin survived, along with emacs and xterm.
It happens intermittently, maybe once every 3 days, and I haven't found
a simple sequence of steps for reproducing it. All I can say for sure
is that I always have more than one mintty running, and they all die.
Marco, are you sure all cygwin processes die when you experience this
problem? Also, since you can reliably reproduce the crash, have you
tried reverting to the previous version of mintty? Note that mintty was
updated just a few days before the 20120619 snapshot was released.
Ken
--
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-06-26 11:53 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 [this message]
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
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=4FE9A2A1.3040802@cornell.edu \
--to=kbrown@cornell.edu \
--cc=cygwin@cygwin.com \
/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).