Author Topic: How does CB determine which debugger option set (gdb/windbg) is to be used?  (Read 5587 times)

Offline doctor_vitus

  • Multiple posting newcomer
  • *
  • Posts: 15
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
« Last Edit: May 24, 2007, 11:37:23 am by doctor_vitus »

Offline mandrav

  • Project Leader
  • Administrator
  • Lives here!
  • *****
  • Posts: 4315
    • Code::Blocks IDE
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...

Offline doctor_vitus

  • Multiple posting newcomer
  • *
  • Posts: 15
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

Offline stahta01

  • Lives here!
  • ****
  • Posts: 7591
    • My Best Post
C Programmer working to learn more about C++ and Git.
On Windows 7 64 bit and Windows 10 64 bit.
--
When in doubt, read the CB WiKi FAQ. http://wiki.codeblocks.org