News:

As usual while waiting for the next release - don't forget to check the nightly builds in the forum.

Main Menu

How does CB determine which debugger option set (gdb/windbg) is to be used?

Started by doctor_vitus, May 24, 2007, 11:32:06 AM

Previous topic - Next topic

doctor_vitus

Hi all!

Currently I'm experiencing problems with the use of the windbg.exe debugger on a Win32 D Application. When I start the debugger, I get three message boxes saying:

The command line option 'nx' is invalid
The command line option 'fullname' is invalid
The command line option 'quiet' is invalid

Several people have asked about this problem before, but I think a solution has not been provided yet.

To me it looks like CB is trying to pass command line parameters to windbg that rather belong to gdb. But to my knowledge, there is also support for windbg in Codeblocks.

So can anybody please tell me how does CB determines whether gdb oder windbg is used (and in fact which command line options have to be passed to the debugger)?

Thanks and best regards,
Vitus

mandrav

This is currently hardcoded. CDB is used for MS compilers and GDB for everything else.
File a feature request.
Be patient!
This bug will be fixed soon...

doctor_vitus

OK.

It would even be helpful if the hardcoded debugger settings for the Digital Mars D compiler on MS Windows would be changed to windbg (but only on MS Windows, as the Linux version of DMD required gdb).

Thanks and best regards,
Vitus

stahta01

C Programmer working to learn more about C++.
On Windows 10 64 bit and Windows 11 64 bit.
--
When in doubt, read the CB WiKi FAQ. [url="http://wiki.codeblocks.org"]http://wiki.codeblocks.org[/url]