Re: procps and pgrep hang

2012-06-07 Thread Tom Rodman
On Wed 6/6/12 19:53 CDT Tom R wrote: --snip > Then, if I 'putty -ssh' (version .60) to the localhost, and then run > > procps -wwH -o pid,ppid,user,tty,args -e > > it hangs. > > So putty triggers it. I'll try a newer version of putty. also hangs w/latest verion: 0.62 of putty > I like being ab

Re: procps and pgrep hang

2012-06-06 Thread Tom Rodman
On Wed 6/6/12 10:04 EDT cgf wrote: --snip > >This morning I tried cygwin-inst-20120604.tar.bz2, and the problem > >shows up in the same way as decribed above for cygwin-inst-20120507.tar.bz2. > > Is putty required to see this hang? Yes. Tonight, I tried cygwin-inst-20120507.tar.bz2 and I s

Re: procps and pgrep hang

2012-06-06 Thread Christopher Faylor
On Wed, Jun 06, 2012 at 07:10:04AM -0500, Tom Rodman wrote: >On Wed 6/6/12 10:08 +0200 Corinna wrote: >> On Jun 5 20:31, Tom Rodman wrote: >> > On Wed 5/30/12 17:53 +0200 Corina wrote: >--SNIP >> > Tonight on my laptop I have been unable to get either problem >> > to show up on the cygwin-inst-201

Re: procps and pgrep hang

2012-06-06 Thread Tom Rodman
On Wed 6/6/12 10:08 +0200 Corinna wrote: > On Jun 5 20:31, Tom Rodman wrote: > > On Wed 5/30/12 17:53 +0200 Corina wrote: --SNIP > > 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

Re: procps and pgrep hang

2012-06-06 Thread Corinna Vinschen
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

Re: procps and pgrep hang

2012-06-05 Thread Tom Rodman
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

Re: procps and pgrep hang

2012-05-30 Thread Corinna Vinschen
On May 30 08:12, Tom Rodman wrote: > On Wed 5/23/12 17:53 +0200 Corinna wrote: > > On May 21 11:40, Tom Rodman wrote: > > > On Wed 5/16/12 22:04 EDT Christopher Faylor wrote: > > > > On Wed, May 16, 2012 at 08:46:09PM -0500, Tom Rodman wrote: > > > > > $ pgrep bash > > > --snip > > > > > $ procp

Re: procps and pgrep hang

2012-05-23 Thread Corinna Vinschen
On May 21 11:40, Tom Rodman wrote: > On Wed 5/16/12 22:04 EDT Christopher Faylor wrote: > > On Wed, May 16, 2012 at 08:46:09PM -0500, Tom Rodman wrote: > > > $ pgrep bash > --snip > > > $ procps -o pid,args > > > PID COMMAND > > > 4580 procps -o pid,args > > > --note: above command hangs, en

Re: procps and pgrep hang

2012-05-16 Thread Christopher Faylor
On Wed, May 16, 2012 at 08:46:09PM -0500, Tom Rodman wrote: >more details > ># example hang (^C will not kill): > > $ pgrep bash > ># tail end of strace of above: > > 37 208960 [main] pgrep 2184 fhandler_process::exists: exists > (/proc/2488/cmdline) > 41 209001 [main] pgrep 2184 build_fh_p

procps and pgrep

2012-05-16 Thread Tom Rodman
After upgrading to 1.7.15(0.260/5/3), on several hosts (but not all) the commands: procps pgrep hang. I will try to follow up w/more details (cygcheck output) in the next couple of days. -- thanks, Tom Rodman -- Problem reports: http://cygwin.com/problems.html FAQ: