The only time I've seen weird things in the IDE is dependant on the
breakpoint location. I've had weird things happen when I break in the
routine that is putting up a menu, for instance. Are you breaking in a
new and unusual location?

> -----Original Message-----
> From: [EMAIL PROTECTED] 
> [mailto:[EMAIL PROTECTED] On Behalf Of Dee Holtsclaw
> Sent: Tuesday, March 30, 2004 7:14 PM
> To: [EMAIL PROTECTED]
> Subject: RE: [msvc] VC6 lockup during debugging
> 
> 
> Don't think so... especially considering that the App works just fine
> outside of the debugger. I was trying to see where some 
> totals got off to
> when I started encountering the problem. I can't find my 
> VC6-SP5 disk so it
> looks like I'll have to download that again tonight (nice to 
> have friends
> with DSL). When I get in tomorrow, I'm going to try 
> reinstalling SP5 then
> the whole MSDEV followed by SP5. If neither works and there's 
> no better
> suggestions, I guess I'll repave the box.
> 
> Still, this is inexcusable. Problems like this are why I am 
> so down on all
> things Redmond.
> 
> Ciao,
> Dee
> 
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] Behalf Of Jason Teagle
> Sent: Tuesday, March 30, 2004 5:46 PM
> To: [EMAIL PROTECTED]
> Subject: RE: [msvc] VC6 lockup during debugging
> 
> 
> > Thanks. I don't get any assertions from the IDE nor is anything
> > in the watch
> > window. The symptoms are (1) the process being debugged 
> does not continue
> > [debugee thread state is Wait:WrLpcReply according to 
> ProcessExplorer] and
> > (2) the IDE becomes completely non-responsive including not 
> repainting the
> > screen or responding to any window messages.
> 
> Bizarrely, I'm working on code as we speak and I just had 
> such a lockup. It
> was caused by an infinite loop I inadvertently introduced 
> *bangs head on
> desk*... any chance you've managed to introduce some new code or code
> changes that could have caused this? Always locks in the same place?
> 
> --
> Jason Teagle
> [EMAIL PROTECTED]



Reply via email to