X-Spam-Check-By:	sourceware.org
Message-ID:	<4457C0DB.F0093A96@dessent.net>
Date:	Tue, 02 May 2006 13:28:11 -0700
From:	Brian Dessent <brian AT dessent DOT net>
X-Mailer:	Mozilla 4.79 [en] (Windows NT 5.0; U)
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	Re: cygwin + windows update = lock up (W2K SP4)
References:	<003e01c66e19$caab4ea0$a501a8c0 AT CAM DOT ARTIMI DOT COM>
X-IsSubscribed:	yes
Reply-To:	cygwin AT cygwin DOT com
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
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:

> ...because for some reason, despite attaching the debugger, and despite having
> frozen every other thread and only left one running, every time I try to
> single step it, it just carries on running as if I'd told it to continue.
> Dunno why except perhaps the debugger isn't keen to try and let you
> single-step through debugger-related functions in case it breaks itself or
> something.  This may call for a full two-machine kernel remote debugging
> session in the end :-(

It's a real shame that Russinovich is apparently aware of this defect
but remains uninterested in dealing with it past calling it a Cygwin
deficiency.

Brian

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

- Raw text -