Menu
▾
▴
#611 Debugger invalid state if debugger executable is invalid
Today, I found out a weird thing with the debugger plugin:
I've had changed the path to the compiler but forgot to adopt the path to the debugger, too. Therefore, there was a debugger config (active) but invalid. when you try to run the debugger in that case you get a very strange behaviour and the icons are being greyed out and don't return for me. Additionally I don't see a warning / error that tells me the path is wrong and the debugger could not be found. You might want to have a look in that. Looks like the debugger ends up in a state where it should't be and can't return...
Hello,
I could reproduce similar behavior, but I'm not sure if it's exactly the same behavior you have outlined. I am running Code::Blocks 17.12 on Windows 10 Version 1709 (Build 16299). I do not know what toolset you are using, but for what it is worth, I am using gcc 7.3 (64-bit on a 64-bit host) via mingw-x64. I could replicate this by selecting "Cygwin GCC" as the compiler used by my project, then selecting the filepath of the mingw version of gcc by going to Settings->Compiler->Global Compiler Settings->Toolchain executables. This did not update the file path for gdb and the icons were greyed out, however I only received a warning after attempting to debug the already compiled binary. The debugger executable could later be specified by going to Settings->Debugger->Default then specifying the filepath in "Executable path".
It may be worthwhile to see if this occurs with msvc and cdb (Microsoft's toolset) as well as clang and llvm (Apple's toolset). I presume most people who use this software are using gcc, so perhaps it's just a gnu issue and not a Code::Blocks issue. Hope it helps.
This should have been fixed in [r12467]. Please reopen if this is not the case.
Related
Commit: [r12467]
SVN12462 nightly build debug log output with invalid GDB.exe name:
Starting debugger: C:\mingw-w64\mingw64\bin\gdb.exe -nx -fullname -quiet -args C:/GM_Work/Testing/Archived/Cygwin_Printf_I64/bin/Debug/Cygwin_OStream.exe
failed
The icons in the case of an invalid GDB.exe return to the same state before running the debugger, which then allows you to fix the debugger and try again.