Re: Save VC++ 6.0 IDE Debug info
From: Oleg Starodumov (oleg_staro_at_hotmail.com)
Date: 02/17/04
- Next message: David Lowndes: "Re: warning LNK4098... how to avoid it when making a static lib?"
- Previous message: Morten Aune Lyrstad: "Re: warning LNK4098... how to avoid it when making a static lib?"
- In reply to: David Partington: "Save VC++ 6.0 IDE Debug info"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 17 Feb 2004 11:03:33 +0200
> Is it possible to save all debugging information (eg. watch window for
> all threads, call stack for all threads, memory, registers ...)
> displayed by the IDE to a file for later examination?.
>
> The problem I am working on is very difficult to reproduce (maybe occurs
> once every few days) and it would be helpful to have records of each
> occurrence to work on.
>
You can use crash dumps to save this information.
Unfortunately VC 6.0 does not allow to create crash dumps, but you can
create them with WinDbg or VS.NET.
WinDbg:
http://www.microsoft.com/whdc/ddk/debugging/default.mspx
(see "Crash Dump Files" in WinDbg help)
VS.NET:
http://msdn.microsoft.com/library/en-us/vsdebug/html/vxtskCrashDumps.asp?frame=true
With WinDbg, it is also possible to save command output to a log file,
so that you can save such information as watches, call stacks, registers, etc.
at any moment of time.
Regards,
Oleg
- Next message: David Lowndes: "Re: warning LNK4098... how to avoid it when making a static lib?"
- Previous message: Morten Aune Lyrstad: "Re: warning LNK4098... how to avoid it when making a static lib?"
- In reply to: David Partington: "Save VC++ 6.0 IDE Debug info"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
