RE: [msvc] VC6 lockup during debugging

Mon, 05 Apr 2004 17:40:53 -0500

I suppose that's a fair analogy. :)
 
The point I was trying to make though was that VA-X, regardless of the source of the crash, didn't seem to trash the source anymore and, in fact, did a right decent job of saving it. I've had the IDE lock up (heck, the whole box for that matter) many times when debugging and using Spy++ at the same time. A combination I've learned to avoid yet, sometimes, it's still the only way to see what's *really* happening.
 
There's still some problems with it [VA-X], especially for this 500,000+ line project I've been working on, but I'm willing to cut them some slack since they have to make this work in a Microsoft-controlled environment -- that can't be an easy task.
 
Regardless, I'm able to get some work done now and feverishly trying to insure my successor has something stable to work with once I'm outta here (tomorrow's my last day).
 
Ciao,
Dee
 
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]On Behalf Of W. Nathaniel Mills, III
Sent: Monday, April 05, 2004 5:51 PM
To: [EMAIL PROTECTED]
Subject: RE: [msvc] VC6 lockup during debugging

So, VA-X was pretty good about saving the code you feared you'd lost due to VA-X causing lockups... did I get this right?  Kind of like thanking yourself after you stop banging your head to cure your headaches isn't it?
 
Glad you're back in business -- those kinds of errors are very frustrating.  Heisenberg debugging...  I remember a guy who'd misplaced the #endif so his code worked great in debug mode but a line was kept from compiling in product mode.
 
Best Regards, we've all been where you just were.  Glad things worked out for you.  Nat
 
Monday, April 05, 2004 1:31 PM
To: <[EMAIL PROTECTED]>
cc:
From: "Dee Holtsclaw" <[EMAIL PROTECTED]>
Subject: RE: [msvc] VC6 lockup during debugging

Just installed VA-X build 1224 and it *appears* the lockups are solved. At
least I was able to complete a full debugging run through with multiple
breakpoints (which was impossible before).
 
Incidentally, although I've had problems with lost text in the past, VA-X
has auto-recovered changes lost via the debugging lockups. So, although the
lockups themselves were insurmountable, I didn't lose a single line of code
in the process. All in all, it's looking pretty good. I think they've about
got it right now.
 
Ciao,
Dee
 
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Phil Daley
Sent: Friday, April 02, 2004 2:45 PM
To: [EMAIL PROTECTED]
Subject: RE: [msvc] VC6 lockup during debugging
 
 
At 4/2/2004 02:10 PM, Dee Holtsclaw wrote:
 
>BTW, by "locking up the system", are you referring to the whole OS (term
>used VERY loosely)? If so, is that the 9X or NT series? I ask because,
>although the IDE locks up incessantly, all other running Apps seem to be
>fine.
 
You are correct, just the MS IDE part.
 
Phil Daley          < AutoDesk >
 
 
 
 
_______________________________________________
msvc mailing list
[EMAIL PROTECTED]
subscription changes, and list archive.
 
 
_______________________________________________
msvc mailing list
[EMAIL PROTECTED]
See http://beginthread.com/mailman/listinfo/msvc_beginthread.com for subscription changes, and list archive.

---
Incoming mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.642 / Virus Database: 410 - Release Date: 3/24/2004

Reply via email to