My case:
1. Project, used on different PC with different compiler:
<Option compiler="nixman_131_ucrt_win32_gnu_gcc_64" />
was opened in C::B.
2. It proposed me to change non-existing compiler with incorrect one.
3. I choose correct.
4. I applied changes on all targets.
Everything looks fine at that moment, but options_gcc.xml was generated. When I opened C::B next time, I got empty compiler flags.
Likely this is an issue from the same origins. GDB for toolchain configured as in attach, from actual 64 bit mingw. In C::B config it is OK:
- <nixman_gcc_132_64__compiler>
- <NAME>
- <str>
- <![CDATA[ Nixman GCC 13.2 64 Compiler
]]>
</str>
</NAME>
- <PARENT>
- <str>
- <![CDATA[ gcc
]]>
</str>
</PARENT>
- <MASTER_PATH>
- <str>
- <![CDATA[ C:\mingw64\nixman13_2w32u
]]>
</str>
</MASTER_PATH>
- <C_COMPILER>
- <str>
- <![CDATA[ x86_64-w64-mingw32-gcc.exe
]]>
</str>
</C_COMPILER>
- <CPP_COMPILER>
- <str>
- <![CDATA[ x86_64-w64-mingw32-c++.exe
]]>
</str>
</CPP_COMPILER>
- <LINKER>
- <str>
- <![CDATA[ x86_64-w64-mingw32-g++.exe
]]>
</str>
</LINKER>
- <DEBUGGER_CONFIG>
- <str>
- <![CDATA[ gdb_debugger:nix64
]]>
</str>
</DEBUGGER_CONFIG>
</nixman_gcc_132_64__compiler>
where "nix64":
- <conf4>
- <NAME>
- <str>
- <![CDATA[ nix64
]]>
</str>
</NAME>
- <values>
- <EXECUTABLE_PATH>
- <str>
- <![CDATA[ C:\mingw64\nixman13_2w32u\bin\gdb.exe
]]>
</str>
</EXECUTABLE_PATH>
<DISABLE_INIT bool="1" />
- <USER_ARGUMENTS>
- <str>
- <![CDATA[
]]>
</str>
</USER_ARGUMENTS>
<TYPE int="0" />
- <INIT_COMMANDS>
- <str>
- <![CDATA[ source $(TARGET_COMPILER_DIR)etc/gdbinit
set print elements 100
]]>
</str>
</INIT_COMMANDS>
<WATCH_ARGS bool="1" />
<WATCH_LOCALS bool="1" />
<CATCH_EXCEPTIONS bool="1" />
<EVAL_TOOLTIP bool="0" />
<ADD_OTHER_SEARCH_DIRS bool="0" />
<DO_NOT_RUN bool="0" />
<DISASSEMBLY_FLAVOR int="0" />
- <INSTRUCTION_SET>
- <str>
- <![CDATA[
]]>
</str>
</INSTRUCTION_SET>
</values>
</conf4>
Actually called "Default" GDB (invalid)
Starting debugger: c:\mingw32\gdb64\bin\gdb.exe -fullname -quiet -args Q:/mingw64/projects/****
failed