> I've been gleefully (ok, not really, but...) debugging several apps I'm
> working on for months without incident. Now suddenly today the IDE keeps
> freezing when I continue after hitting a breakpoint. There have been no
> framework crashes yesterday or today and the only thing that has been
> installed ('bout forgot about this) was LookOut! insisting on
> installing the
> Hebrew language pack when it encountered an email in the OffTopic
> list from
> Roy Osherove.
>
> I *really* don't have the time to repave my box right now and nothing else
> seems to be having problems except for the IDE. Any ideas anyone?Wild shot: I don't know about lockups, but I did have a situation once or twice where breaking at a breakpoint I had (deliberately) set caused the IDE to issue an ASSERT inexplicably. It took me a while to figure out, but it was because one of the expressions I had in the user watch window was something like m_aryStrLines.GetAt(n) - I was using it to see what CString was at a position in the CStringArray in a certain context elsewhere, but at this breakpoint the variable was now out of the intended context and so n was beyond the actual storage space allocated in the CStringArray (imagine that the same array name was available at both places, so the debugger would try to evaluate the expression). Thus, it was asserting when it tried to update the watched value from this expression, throwing me right off-course. The moral of what I'm trying to say, is, be sure none of your expressions in the user watch window is doing something dodgy. -- Jason Teagle [EMAIL PROTECTED]
