Author Topic: New installation, debugger missing  (Read 117 times)

Offline mdean

  • Single posting newcomer
  • *
  • Posts: 1
New installation, debugger missing
« on: February 09, 2019, 07:23:46 am »
I used to use Code::Blocks to make C++ programs for Project Euler.  The hard drive on my last computer died, however, and the rest of the computer was  obsolete, so the computer was replaced and, today, I attempted to find and install Code::Blocks on this new system.  I downloaded codeblocks-17.12mingw-setup.exe and did the full install, unchecking nothing.  I wrote my program, got the wrong result, and tried to debug it.  In the window below, I got the following red text:

Quote
ERROR: You need to specify a debugger program in the debuggers's settings.
(For MinGW compilers, it's 'gdb.exe' (without the quotes))
(For MSVC compilers, it's 'cdb.exe' (without the quotes))


I went to Settings, then Debugger.  In the Default section under GDB/CDB debugger, the first item is Executable Path, which is red and blank.  Hovering over this item reveals a message "Full path to the debugger's executable.  Executable can't be found on the filesystem!"  I checked the location where Code:Blocks was installed.  I found a MinGW subfolder which in turn had a gdb32 subfolder.  Actually, while in the process of creating this message, I found a gdb32.exe in the bin subfolder of gdb32.  I assume this is the file that it wants?


I apologize it this should be in the Using Code:Blocks topic because I understand very little of this stuff or under bugs if this should have been set up by the installer.  Not sure if this is an oversight or my own ignorance.  I did do a brief search and didn't notice any similar issue.

Offline ollydbg

  • Developer
  • Lives here!
  • *****
  • Posts: 5208
  • OpenCV and Robotics
    • Chinese OpenCV forum moderator
Re: New installation, debugger missing
« Reply #1 on: February 09, 2019, 09:00:08 am »
...
I assume this is the file that it wants?
...
Yes, you are correct.

If some piece of memory should be reused, turn them to variables (or const variables).
If some piece of operations should be reused, turn them to functions.
If they happened together, then turn them to classes.