C::B 25.03 Multiple Debuggers selection old bug still there.

[MasterAlexei]

Hello everyone,
Since 20.03 (and I think it is yet earlier) there is a bug on selection of Debugger for current Project/Target.
I have several Debuggers in Debug Setting (I total 8 in my compilers Zoo), and each Project has its own Compiler and logically its own debugger.

By clicking "Start Debug" it will always the second one taken, which is listed in default.conf under <sets> ... <gdb_debugger> ... <conf2>.

The only way I found to start the right Debugger is ... modifying the default.conf file so that needed Debugger is in <conf2> config is (i.e. rename <confX> group.
It is a bit annoying by switching projects to restart whole C::B.

Sorry if I was wrong with the thread in a Forum. I am seldom guest here.
The Berlios Bug Trackes shows 500 Internal Server Error.

[Pecan]

MainMenu>debug>active debugger>selectDebug config

[MasterAlexei]

Oh man, that is a bit hidden under menus. I do start debug sessions via shortcut F8 or a tool button with mouse. This menu "Debug" is a seldom place to visit...

Thanks. Now I learned some thing more.

[MasterAlexei]

But then, the ability to choose Debugger in a "Compiler Settings" makes no sense.

As I remember, in earlier versions, the current debugger was selected by selecting the "Build target" to build, and in a "Build Options" the compiler is selected, and in a "Compiler setting" is a debugger defined for that particular compiler.

It is a bit misleading to have separate Build target selection and Debugger selection, along with the ability to set debugger in a "Compiler settings", that has no effect then.

[Pecan]

But then, the ability to choose Debugger in a "Compiler Settings" makes no sense.

As I remember, in earlier versions, the current debugger was selected by selecting the "Build target" to build, and in a "Build Options" the compiler is selected, and in a "Compiler setting" is a debugger defined for that particular compiler.

It is a bit misleading to have separate Build target selection and Debugger selection, along with the ability to set debugger in a "Compiler settings", that has no effect then.

Yeah, there's been some fiddling around in that area of the code. But that fiddler is no longer around.

Could you just copy some of this thread and make a ticket of it.
I'm working on debugger_DAP and if/when I get into that area and fix it, I'll make a backport also.

Thanks