From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: procps and pgrep hang
Date: Wed, 06 Jun 2012 08:10:00 -0000 [thread overview]
Message-ID: <20120606080849.GC23539@calimero.vinschen.de> (raw)
In-Reply-To: <201206060131.q561VOHa009097@localhost.localdomain>
On Jun 5 20:31, Tom Rodman wrote:
> On Wed 5/30/12 17:53 +0200 Corina wrote:
> --SNIP
> > > On my laptop, only the pgrep bug shows up, here is the 'forever hang'
> > > strace w/CYGWIN set to pipe_byte:
> >
> > A signal delivery hangs as if the receiver never reads its signal pipe.
> > I still can't reproduce the problem, though. Can you try to find out
> > which snapshot introduced the problem?
>
> Tonight on my laptop I have been unable to get either problem
> to show up on the cygwin-inst-20120504.tar.bz2 snapshot.
>
> To get the hang to show up on the cygwin-inst-20120507.tar.bz2
> snapshot. I start a rxvt, and then 'net start sshd', putty (ssh) to the
> localhost using public key trust, then ran:
And the same occurs under a recent snapshot?
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Project Co-Leader cygwin AT cygwin DOT com
Red Hat
--
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-06 8:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-16 16:51 procps and pgrep Tom Rodman
2012-05-17 1:47 ` procps and pgrep hang Tom Rodman
2012-05-17 2:04 ` Christopher Faylor
2012-05-21 16:42 ` Tom Rodman
2012-05-23 15:57 ` Corinna Vinschen
2012-05-30 14:13 ` Tom Rodman
2012-05-30 15:58 ` Corinna Vinschen
2012-06-06 1:32 ` Tom Rodman
2012-06-06 8:10 ` Corinna Vinschen [this message]
2012-06-06 12:10 ` Tom Rodman
2012-06-06 14:04 ` Christopher Faylor
2012-06-07 0:54 ` Tom Rodman
2012-06-07 13:29 ` Tom Rodman
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=20120606080849.GC23539@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--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).