I've experienced the break-point delay -- most significant being inserting or removing lines from source which contains breakpoints lower in the file. I've also occasionally had it mung my source by double spacing the entire file.
The only plug-in presently installed is VisualAssistX and it has twice recovered changes lost by the IDE during these debug-time lockups. VA-X has worked fine (other than some major annoyances I've been hounding WholeTomato over) and appears to still be doing so. Didn't really have any problems with it until Tuesday. Of course I've learned to expect whole-system lockups when debugging in conjunction with Spy++, but that's not been loaded since at least a week ago (yes, I locked it up once then). Anyway, I've installed W2K-SP4 now and the problem still exists. I've also disabled VA-X and the problem still occurs. Hmmm... Completely *UNLOADING* VA-X makes it all better... Checking WholeTomato website... Updating to latest release... D***! Still locks up, but only when VA-X is loaded. Looks like I need to be bitching about VA-X instead of vacillating over repaving the box. I'll keep everyone updated. Is anyone else here using VisualAssistX? Ciao, Dee -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Jason Teagle Sent: Thursday, April 01, 2004 8:48 AM To: [EMAIL PROTECTED] Subject: RE: [msvc] VC6 lockup during debugging > We have had a problem with setting a bunch of break points (> 20) > and then > the debugger taking 30-40 minutes to start up. While we're all listing difficulties with the IDE, I have found that if I hit F7 to compile too quickly after I've just made a change to a file and manually saved it (I manually save after each chunk of changes for fear of losing the file), it can sometimes get in a real twist and ends up in a stuck state (the IDE, that is). It seems to be something to do with it trying to use the file for a short moment after it has changed to update other areas (for example, the Class View). Now I try and consciously give it a couple of seconds after a save before trying to compile. -- Jason Teagle [EMAIL PROTECTED]
