This is the mail archive of the
mailing list for the Cygwin project.
Re: 100% CPU with recent snapshots
- To: cygwin at sourceware dot cygnus dot com
- Subject: Re: 100% CPU with recent snapshots
- From: Rick Rankin <rick_rankin at yahoo dot com>
- Date: Thu, 24 Feb 2000 15:14:24 -0800 (PST)
Thanks, Chris. I was starting to consider trying to track it down, but with my
limited resources (read: time) and total unfamiliarity with the code, it would
have taken a while. I'm also fairly unfamiliar with debugging Windows DLLs,
although I assume it must be somewhat similar to debugging shared libraries on
Frankly, I'm glad someone had an idea about this problem. As I have time, I
hope to start playing around with the DLL code, building the DLL, etc., so I
won't feel so helpless the next time something goes wrong (assuming it does
--- Chris Faylor <email@example.com> wrote:
> On Wed, Feb 23, 2000 at 06:20:07PM -0500, cgf wrote:
> >On Wed, Feb 23, 2000 at 09:06:19AM -0800, Rick Rankin wrote:
> >>With the recent snapshots (i.e., those I've tried since about 01/08), I've
> >>noticed that when I start bash in a cmd.exe window, my CPU usage goes to
> >>With the *very* recent snapshots (02/11, 02/21), I don't even get a prompt.
> >>window appears with the cursor flashing in the upper left corner, but no
> >You're not seeing any reply because merely posting an observation does not
> >provide enough information to solve a problem.
> >I've seen a lot of email from people saying "I tried the 7-15-99 version
> >and it works and I tried the 1-15-2000 and it fails!" but I haven't gotten
> >anything from anyone who has attempted to debug the problem.
> >If someone wants to debug this then I'd be interested in hearing the
> >It's not likely to be fixed otherwise.
> Corinna gave me enough information to try to fix this problem. An attempt
> at a fix should be in tonight's snapshot.
Do You Yahoo!?
Talk to your friends online with Yahoo! Messenger.
Want to unsubscribe from this list?
Send a message to firstname.lastname@example.org