Recent Posts

51

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

« Last post by Pecan on November 02, 2025, 02:10:31 am »

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

52

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

« Last post by MasterAlexei on November 02, 2025, 01:54:20 am »

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.

53

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

« Last post by MasterAlexei on November 02, 2025, 12:02:02 am »

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.

54

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

« Last post by Pecan on November 01, 2025, 11:40:33 pm »

MainMenu>debug>active debugger>selectDebug config

55

Using Code::Blocks / Re: How to configure Perf profiler and Hotspot as external tool on Linux

« Last post by cdavalillo on November 01, 2025, 04:24:38 pm »

In the script the line

Code

perf record --call-graph dwarf -o "$PERF_DATA_PATH" \
  env LD_LIBRARY_PATH="$LIB_DIR:$LD_LIBRARY_PATH" "$EXE_PATH"

Might not work well in some cases then just remove the env part so it would be like

Code

perf record --call-graph dwarf -o "$PERF_DATA_PATH" "$EXE_PATH"

56

Development / Re: AI may help us to create plugins

« Last post by ollydbg on November 01, 2025, 02:13:13 pm »

Generated wiki looks nice, I'm hearing about deepwiki first time, looks very useful tool. Thank you for sharing.

Regarding the plugin generated, how complete was the code?

I'm also new to d :)eepwiki site.

I haven't tried the generated code yet, but you can see this page:

https://deepwiki.com/search/can-you-help-me-to-create-a-co_35be54bd-5f47-4e3b-ba7d-bdff22584a0e

Just scroll down to the bottom of the page, it has many source code generated, and the code looks good.

57

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

« Last post by MasterAlexei on November 01, 2025, 11:59:44 am »

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.

58

Development / Re: AI may help us to create plugins

« Last post by christo on November 01, 2025, 06:22:53 am »

Generated wiki looks nice, I'm hearing about deepwiki first time, looks very useful tool. Thank you for sharing.

Regarding the plugin generated, how complete was the code?

59

Development / AI may help us to create plugins

« Last post by ollydbg on October 31, 2025, 04:18:23 pm »

Hi, I recently see a website named deepwiki, this site can read a github project, and later, it can have LLM powered AI chat about this project. As a test, I just put the code::blocks' source code to the index, see: https://deepwiki.com/asmwarrior/codeblocks_sfmirror

After that, I just wrote some text to AI:

can you help me to create a code::blocks plugin which can run the memory leak detector mentioned here: https://github.com/ssbssa/heob

And I see that it can create the source code for this plugin, looks interesting. 

60

Development / C::B 25.03 from SVN compile error cannot find -lexchndl.dll

« Last post by MasterAlexei on October 31, 2025, 02:56:05 pm »

Hello everyone,
I try to compile C::B 25.03 from SVN tag, on Win10. with wxWidgets 3.1.3 in 32 Bit mode with MinGW32 12.2.0 via old C::B (20.03)
By building "src" Target the linker says  that the exchndl.dll can not be found, but it is there both libexchndl.dll and libexchndl.dll.a files are present.
I think that there is a Version match problem of the libexchndl.dll.a file, because it is a precompiled binary (exchndl) and MinGW may not find a libs, if they are compiled with other versions.

The question is, which Version of MinGW schould I take, to compile C::B 25.03 from SVN tag, on Win10. with wxWidgets 3.1.3 in 32 mod.
I already tried  x86_64-12.2.0-release-win32-seh-msvcrt-rt_v10-rev2, x86_64-12.2.0-release-posix-seh-ucrt-rt_v10-rev2 and some 13.1.0 Versions.

Thank you in advance,
Alexey

Small Update on next day:
with the MinGW Version gcc-12.2.0 --arch=i686 msvcrt-dwarf-win32 dwarf --rt-version=v10 --threads=win32
this issue with libexchndl.dll is gone (it is found and links)

BUT

In a BrowseTracker Plugin there is a compile Error is popped out:
BrowseTracker.h|383|error: 'mutex' in namespace 'std' does not name a type

I compile from old C::B it means, that all compile Params (such as -std=gnu++11 ) are set from the C::B Team.
The problem here is that, if I use MinGW with higher version, this error with mutex is then gone, but pooped the error with ibexchndl.dll.

How do the C::B Team compile this C::B 25.3 ?