Hi all,
I've been trying to get WinDbg to work with CB so that I can use existing Visual Studio C++ V6 projects with minimal change other than using CB instead of VS as the IDE.
I have downloaded and installed the Microsoft Debuggers from
http://www.microsoft.com/whdc/devtools/debugging/default.mspx and have set the toolchain executables to point to "C:\Program Files\Debugging Tools for Windows" which is where WinDbg and the other debuggers reside.
I then built a sample program in Debug mode and then tried to debug it. Whenever I invoke Debug or "Run to Cursor" etc I get the WinDbg help screen displayed, showing the command line options that are available. The debugger log window in CB contains:
Command-line: C:\Program Files\Debugging Tools for Windows\windbg.exe -G -lines -y c:/tmp/hello/; -srcpath c:/tmp/hello/; bin/Debug/hello.exe
Working dir : c:\tmp\hello\
Command-line: C:\Program Files\Debugging Tools for Windows\windbg.exe -G -lines -y c:/tmp/hello/; -srcpath c:/tmp/hello/; bin/Debug/hello.exe
Working dir : c:\tmp\hello\Looking at the WinDbg help screen:
-G
(User mode only) Ignores the final breakpoint at process termination. Typically, the debugging session ends during the image run-down process. This option will cause the debugging session to end immediately when the child terminates. -y SymbolPath
Specifies the symbol search path. Separate multiple paths with a semicolon (
. If the path contains spaces, it should be enclosed in quotation marks. For details, and for other ways to change this path, see Symbol Path. srcpath SourcePath
Specifies the source file search path. Separate multiple paths with a semicolon (
. If the path contains spaces, it should be enclosed in quotation marks. For details, and for other ways to change this path, see Source Path. but no description of
-lines.
The question is: what else to I have to do to get WinDbg working with CB? Any help would be greatly appreciated.
Cheers,
Joseph