From: Brian Ford <ford@vss.fsi.com>
To: cygwin@cygwin.com
Subject: Re: [OT] RE: Problems listing tasks under cygwin.
Date: Wed, 19 May 2004 14:03:00 -0000 [thread overview]
Message-ID: <Pine.CYG.4.58.0405190842250.2628@fordpc.vss.fsi.com> (raw)
In-Reply-To: <40AB2792.A4AB6650@dessent.net>
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/
next prev parent reply other threads:[~2004-05-19 13:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-18 8:07 alejandro.sanchez
2004-05-18 16:58 ` Larry Hall
2004-05-18 17:03 ` Dave Korn
2004-05-18 18:40 ` Brian Dessent
2004-05-18 18:49 ` Igor Pechtchanski
2004-05-19 9:23 ` [OT] " Dave Korn
2004-05-19 9:29 ` Brian Dessent
2004-05-19 14:03 ` Brian Ford [this message]
2004-05-20 13:22 ` Dave Korn
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=Pine.CYG.4.58.0405190842250.2628@fordpc.vss.fsi.com \
--to=ford@vss.fsi.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).