Developer forums (C::B DEVELOPMENT STRICTLY!) > Plugins development
C::B and MS 2005 free compiler?
L_O_J:
--- Quote from: sethjackson on August 11, 2006, 11:09:20 pm ---I believe the Microsoft debugger is called CDB......
http://www.microsoft.com/whdc/devtools/debugging/default.mspx
--- End quote ---
well I'm using C::B with MingW and VC++ Express 2005, C::B recognize the cdb (in the compiler option window) but it seems that C::B doesn't now how to use it (or doesn't use it at all).
godcode:
yeah. i tried also using the Borland 5.5 compiler and CodeBlocks wouldnt want to use it too...
mandrav:
Here are some facts regarding debugging with C::B nightlies.
C::B acts as a frontend for two debuggers: GDB and CDB.
CDB is automatically used for projects/targets built using one of the MSVC* compilers. Read below for preparing C::B for CDB.
GDB is used for every other binary. In other words: if it's not determined to be built using a MSVC* compiler, GDB is used.
GDB support is much better than CDB. With CDB, you can do basic stuff like setting breakpoints, watching variables, stepping, continuing, etc.
For C::B to use CDB, it must be able to find it. So, you have to install the Microsoft Debugging Tools for Windows and then add the installation path to the "Additional paths" in the MSVC* compiler's options (in default installations, this path is "C:\Program Files\Debugging Tools for Windows").
If you do the above and still have problems running CDB, ask away (giving as much info as possible).
GeertVc:
--- Quote from: mandrav on August 14, 2006, 08:56:01 am ---For C::B to use CDB, it must be able to find it. So, you have to install the Microsoft Debugging Tools for Windows and then add the installation path to the "Additional paths" in the MSVC* compiler's options (in default installations, this path is "C:\Program Files\Debugging Tools for Windows").
If you do the above and still have problems running CDB, ask away (giving as much info as possible).
--- End quote ---
Hi Mandrav,
To use C::B with the M$ debugging tools, I've followed a tutorial I downloaded a while ago from the site gametutorials.com. Unfortunately, it doesn't seem to be "free" anymore. It's now part of a CD they're selling (if you want, I can still send it to you, but it's quite big: 22.5MB zipped).
In there, it's nicely explained how to set up C::B with the Platform SDK (PSDK-x86) and the M$ Visual C++ Visual toolkit 2003.
Since this toolkit is not supported anymore by M$ (replaced by the newer an free(!!!) Visual Studio Express 2005 line), I looked to one of the threads above to install a "new" compiler, named Visual Studio Express 2005.
I followed this guideline, but I posted a message here in this thread (see some messages before this one) to mention things don't work fine...
Now I see you're talking about another M$ debugger: "Microsoft Debugging Tools for Windows". Is this newer/better/different to the free Express 2005 compiler? Is this the debugger we have to install iso. the Express 2005, like it is mentioned a few messages above?
Pls. clarify if possible, because it's a bit "blurred" for me now.
Best rgds,
--Geert
mandrav:
--- Quote ---Now I see you're talking about another M$ debugger: "Microsoft Debugging Tools for Windows". Is this newer/better/different to the free Express 2005 compiler? Is this the debugger we have to install iso. the Express 2005, like it is mentioned a few messages above?
--- End quote ---
OK, let's get some things straight first.
The Visual* Microsoft IDEs use the Ms debuggers "natively", i.e. communicating with the debugger DLLs through an API of some sort.
We don't have access to those DLLs and/or the API. So we must interface through a command-line frontend for the debugger. Much as we do with GDB.
This command-line frontend is cdb.exe. I don't know if it's part of the Visual* IDE editions. If you have one of them you can check for yourself. If it's there, no problem, put its path in "Additional paths" and it should work (assuming it is using the same text-interface as the standalone cdb.exe provided by Debugging Tools for Windows).
But, if cdb.exe is not on your hard disk, you must install the Debugging Tools for Windows which contain it, as said in my previous post.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version