From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13893 invoked by alias); 19 May 2004 13:54:24 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 13631 invoked from network); 19 May 2004 13:54:21 -0000 Received: from unknown (HELO esds.vss.fsi.com) (66.136.174.212) by sourceware.org with SMTP; 19 May 2004 13:54:21 -0000 Received: from fordpc.vss.fsi.com (fordpc [198.51.27.93]) by esds.vss.fsi.com (8.11.6+Sun/8.9.1) with ESMTP id i4JDsKC26709 for ; Wed, 19 May 2004 08:54:20 -0500 (CDT) Date: Wed, 19 May 2004 14:03:00 -0000 From: Brian Ford Reply-To: cygwin@cygwin.com To: cygwin@cygwin.com Subject: Re: [OT] RE: Problems listing tasks under cygwin. In-Reply-To: <40AB2792.A4AB6650@dessent.net> Message-ID: References: <40AB2792.A4AB6650@dessent.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-IsSubscribed: yes X-SW-Source: 2004-05/txt/msg00677.txt.bz2 On Wed, 19 May 2004, Brian Dessent wrote: > Although I'd still like to know why using ProcExp to list the handles* Nope, it is DLLs. > of any running Cygwin process causes the CPU to peg to 100%, and not > come down until cygwin1.dll is unloaded, i.e. kill all running cygwin > tasks and services. I've had to train myself when using ProcExp to > never accidently click on any Cygwin process, otherwise I have to go > through the annoying process of closing all rxvt's and stopping all > cygservices in order to get an idle CPU again... I don't quite see that. Only the process being explored runs away. After killing it, all is normal. > I've seen this reported to the list before but it got no replies. IIRC, I think I was the first to report it and you were the only one who replied. I haven't tried to fix it yet. > It started several notches back in the 1.5 series when there were a > large number of changes to the signal handling code, IIRC. Agreed. > [*] It could be listing DLLs that causes it, but I don't want to find > out at the moment. It's not that destructive as it only affects the process being explored. Note that the DLLs are not able to be listed, though. -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International the best safety device in any aircraft is a well-trained pilot... -- 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/