cygwin + windows update = lock up (W2K SP4)

[Brian Dessent]

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/