X-Spam-Check-By: sourceware.org
Date: Wed, 26 Apr 2006 17:58:19 -0500
From: mwoehlke <mwoehlke-nospam AT tibco DOT com>
Subject: Re: "Ghost" processes on Cygwin
In-reply-to: <444FF6C8.50707@tibco.com>
To: cygwin AT cygwin DOT com
Reply-to: cygwin AT cygwin DOT com
Message-id: <444FFB0B.3020504@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: <444FF04F DOT 20109 AT tibco DOT com> <444FF238 DOT 40906 AT scytek DOT de>  <444FF6C8 DOT 50707 AT tibco 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

mwoehlke wrote:
> Volker Quetschke wrote:
>> mwoehlke wrote:
>>> I'm seeing something funny. While trying to build a large program on 
>>> Cygwin using cl.exe (i.e. I am building a non-Cygwin app; just using 
>>> Cygwin to drive 'make'), every now and then, cl.exe hangs. Before you 
>>> tell me I'm on the wrong list :-), here's the funny part. If I do 
>>> 'ps' in Cygwin, I can see the 'cl' process, along with its WINPID. 
>>> However, it doesn't show up in task manager! Also, there are about 
>>> five processes that are clearly Cygwin processes (bash.exe or sh.exe) 
>>> that do NOT show up in Cygwin's 'ps'.
>> Can you enter
>> $ ls /proc/*/fd
>> in another cygwin console and report if it helps? It might unhang the 
>> stuck
>> process.
> 
> Hmm... nope. In fact, that got stuck too. 'ls /proc/2072' dies and must 
> be 'kill -9'd. 'ps | grep 2072' says:
>    PID  PPID  PGID WINPID  TTY  UID    STIME COMMAND
>   2072     1  1876   2072  con 1003   Apr 21 /usr/bin/bash

It looks like this process was orphaned somehow... it wouldn't 'kill' or 
'kill -9', so I used task manager to end it, which didn't seem to affect 
any of my active sessions. 'ls /proc/*' and 'ls /proc/*/fd' both work 
now, but don't help.

I should mention that it dies politely if I send it just about any 
signal, but I need it to NOT get stuck in the first place... so I either 
want to figure out why it's hanging, or at least how to try to debug it.

-- 
Matthew
All of my signatures are 100% original. Including this one.

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