X-Spam-Check-By: sourceware.org
Date: Thu, 27 Apr 2006 09:52:42 -0500
From: mwoehlke <mwoehlke-nospam AT tibco DOT com>
Subject: Re: Call for testing Cygwin snapshot
In-reply-to: <000501c669f4$a5dc4210$a501a8c0@CAM.ARTIMI.COM>
To: cygwin AT cygwin DOT com
Reply-to: cygwin AT cygwin DOT com
Message-id: <4450DABA.5090306@tibco.com>
MIME-version: 1.0
Content-type: text/plain; charset=ISO-8859-1; format=flowed
Content-transfer-encoding: 7BIT
User-Agent: Thunderbird 1.5 (X11/20051201)
References:   <20060426122030 DOT fb30e530d17747c2b054d625b8945d88 DOT b260285d48 DOT wbe AT email DOT secureserver DOT net>  <000501c669f4$a5dc4210$a501a8c0 AT CAM DOT ARTIMI DOT COM>
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

Dave Korn wrote:
> On 26 April 2006 20:21, Jerry D. Hedden wrote:
>> In this case, I used the full 20060426 snapshot and generated some stuck
>> processes.  The output from 'ps' showed the following:
>>
>>       PID    PPID    PGID     WINPID  TTY  UID    STIME COMMAND
>>      2944       1    1332      29292    ? 78809 13:54:03 /usr/bin/diff
>>     32184       1     436       2860    ? 78809 14:00:03 /usr/bin/mv
>>      1560       1   28372      29084    ? 78809 14:06:05 /usr/bin/diff
>>      9768       1   23420      24436    ? 78809 14:12:04 /usr/bin/diff
>>
>> Looking at the Windows Task Manager, those processes were not listed,
>> but what I suppose to be their shell processes were:
>>
>> Image Name      PID
>> bash.exe        2736
>> bash.exe        9500
>> bash.exe       29048
>> bash.exe       30324
>>
>> Note that no bash processes were listed by Cygwin under 'ps'.  (Is this
>> a clue?)
> 
>   Um.  I wonder if those processes are or aren't actually there.
> 
>   Isn't there something about bash keeping a pid table of recently-dead
> kind-of-zombie processes hanging around for a while?  Do they show up in "ps"?
> I have a vague memory but haven't tracked down the thread yet.  EB or CV might
> be able to weigh in on this.

Hmm, that sounds almost exactly like my problem. I'm seeing a large 
'make' process occasionally get stuck[1], except the process that 
*seems* to be stuck shows up in 'ps', but not task manager. Sound familiar?

One additional nugget is that I left it "stuck" over night; when I came 
back this morning, I found a 'bash' that had been spawned by 'make' 
where there shouldn't have been any (it should have exec()'d itself out 
of existence). This sounds like the same problem.

I'm running what should be the latest release (minus any updates in the 
last few days), however, not a snapshot; see [1] for my cygcheck output.

[1] http://cygwin.com/ml/cygwin/2006-04/msg00801.html

-- 
Matthew
Ok, so the quotes aren't entirely original.

--
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/