From: Eric Blake <ebb9@byu.net>
To: cygwin@cygwin.com
Subject: Re: Funny hang with snapshop 20050920
Date: Mon, 26 Sep 2005 13:33:00 -0000 [thread overview]
Message-ID: <4337F1FC.3000907@byu.net> (raw)
In-Reply-To: <20050924001110.GA1390@trixie.casa.cgf.cx>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
According to Christopher Faylor on 9/23/2005 6:11 PM:
>
> There is a new snapshot up there now. I think I've given up on the
> technique that I was trying to use to fix the Windows 98 bug. I've
> yanked out a lot of the code and simplified things but I hope I haven't
> caused the bug to reemerge.
>
> Could you try the 2005-09-23 snapshot? Same rules. I'd still like to
> know if sending a CONT to the hung process fixes it as well as ls
> /proc/nnn/fd and I'd still like to see the strace output if the process
> hangs again.
>
> Also could anyone who could duplicate the Windows 98 error popup dialog
> confirm or deny if it is still fixed?
I ran 20050923 on my Win98 box most of the weekend. The original report
of failures to close the console after using ssh still remain fixed; I was
no longer getting popup boxes and was able to close the console. However,
when running process-intensive tasks (such as building coreutils CVS), I
got quite a few blue screens of death, which is new (and worse than a
popup box). I haven't had a chance to try the 20050925 snapshot to see if
it improves matters. I haven't downloaded the snapshot cygwin-inst
recently, so I'm not sure if the recent strace improvements help, but at
least with 20050923, 'strace -o strace.out cvs up' didn't raise a popup
box. I'll continue investigations with more recent snapshots as time permits.
- --
Life is short - so eat dessert first!
Eric Blake ebb9@byu.net
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFDN/H884KuGfSFAYARAhzhAJ96FYOk0INGY5cj/lYMQOYNuOZWdACdE7uI
pws9Kpo4Hc3r1q+3wUiL56s=
=bIEN
-----END PGP SIGNATURE-----
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
next prev parent reply other threads:[~2005-09-26 13:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-23 3:09 Volker Quetschke
2005-09-23 6:09 ` Christopher Faylor
2005-09-23 7:08 ` Volker Quetschke
2005-09-24 0:42 ` Volker Quetschke
2005-09-24 1:11 ` Christopher Faylor
2005-09-26 13:33 ` Eric Blake [this message]
2005-09-26 13:35 ` Christopher Faylor
2005-09-27 11:25 ` Aaron Humphrey
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=4337F1FC.3000907@byu.net \
--to=ebb9@byu.net \
--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).