Tip - Using WinDbg we can detach a process which is attached for debugging. This is useful when debugging big projects.
Details - When debugging VC++6 projects we find it is not possible to detach a process from debugger once we start/attach to debugger. We can overcome this limitation by using WinDbg. WinDbg have almost similar interface and features of msdev debugger, but it is more powerful with features like core dump analysis. It have a menu to detach process so that we can free the process from debugger. Windbg will preserve the breakpoints we set, so that we can use them in future when we start/attach the process. Before starting debug, make sure that File->SymbolPath and File->SourcePath are set in WinDbg
References -
http://www.microsoft.com/whdc/devtools/debugging/default.mspx
http://www.codeproject.com/KB/debug/windbg_part1.aspx
Posted by - Binu Jose
Details - When debugging VC++6 projects we find it is not possible to detach a process from debugger once we start/attach to debugger. We can overcome this limitation by using WinDbg. WinDbg have almost similar interface and features of msdev debugger, but it is more powerful with features like core dump analysis. It have a menu to detach process so that we can free the process from debugger. Windbg will preserve the breakpoints we set, so that we can use them in future when we start/attach the process. Before starting debug, make sure that File->SymbolPath and File->SourcePath are set in WinDbg
References -
http://www.microsoft.com/whdc/devtools/debugging/default.mspx
http://www.codeproject.com/KB/debug/windbg_part1.aspx
Posted by - Binu Jose
No comments:
Post a Comment