Recent Posts

71

Help / Re: Debugger lldb.exe exits without running target executable

« Last post by Pecan on July 29, 2026, 09:38:38 pm »

Thanks for your reply.  As I understand it, there's no way to get the LLVM debugger to work with code::blocks (barring going into the C::B source code and implementing support).  Is that correct?

There is already a debugger being developed for CodeBlocks that supports llvm.
The debugger_DAP source is at https://github.com/pecanh/debugger_DAP.
The setup for the debugger is the same as for debugger_gdb or debugger_gdbmi.

Once the plugin is loaded by CodeBlocks, a settings/debugger entry will appear and you will have
to set the location of your debugger (see attachment).

You also have to decide what flavor of breakpoint.symbols to use.

The ususal -g flag alone will not work for llvm.
You have to match the compiler with the gdb symbol types expected.

Look into the compiler setup for the llvm flag types.


Place the source of the debugger_DAP into the contrib plugin folder.
Review the .cbp file to fit your environment.
Compile and place the plugin into the output32_xx.plugin folder or into the devel32_xx folder to test.
You can use the regular debugger_gdb or debugger_gdbmi to debug debugger_DAP if necessary.

72

Nightly builds / Re: The 27 July 2026 build (13924) is out.

« Last post by christo on July 29, 2026, 07:52:45 pm »

     - Error clangd client : A path containing clang has not been found (seem easy to resolve : add this path into settings clangd client with menu indicated)

Hi @ThierryD, could you please share the path of  clangd binary? It should be autodetected if it is in standard paths, else it is a bug.

     - An assertion failed! ./src/unix/fswatcher_inotify.cpp(66): assert in init(): File system watcher needs an event loop (I bypass this by click on "continue" button)

I could not reproduce the crash in ubuntu 24.04 with Xaviou's ppa (25.03+svn13924~ubuntu24.04.1). Is this issue seen only once, or is it seen on when ever codeblocks is opened?

73

Help / Re: Debugger lldb.exe exits without running target executable

« Last post by MadDavid on July 29, 2026, 07:29:23 pm »

Thanks for your reply.  As I understand it, there's no way to get the LLVM debugger to work with code::blocks (barring going into the C::B source code and implementing support).  Is that correct?

74

Nightly builds / Re: The 27 July 2026 build (13924) is out.

« Last post by Xaviou on July 29, 2026, 06:55:44 pm »

Hi.

Just two signals about this last nightly (13924) on Linux Mint 22.3 Zena (near Ubuntu 24.04)
     - Error clangd client : A path containing clang has not been found (seem easy to resolve : add this path into settings clangd client with menu indicated)
     - An assertion failed! ./src/unix/fswatcher_inotify.cpp(66): assert in init(): File system watcher needs an event loop (I bypass this by click on "continue" button)

The second signal is also a problem with the Clangd_Client plugin (tested on Debian: the message appears if the plugin is enabled)

Regards
Xav'

75

Nightly builds / Re: The 27 July 2026 build (13924) is out.

« Last post by ThierryD on July 29, 2026, 06:32:28 pm »

Hi Xaviou,

Just two signals about this last nightly (13924) on Linux Mint 22.3 Zena (near Ubuntu 24.04)
     - Error clangd client : A path containing clang has not been found (seem easy to resolve : add this path into settings clangd client with menu indicated)
     - An assertion failed! ./src/unix/fswatcher_inotify.cpp(66): assert in init(): File system watcher needs an event loop (I bypass this by click on "continue" button)

and CB start "normally" ...

Regards.

PS : cat /etc/lsb-release
DISTRIB_ID=LinuxMint
DISTRIB_RELEASE=22.3
DISTRIB_CODENAME=zena
DISTRIB_DESCRIPTION="Linux Mint 22.3 Zena"

76

Plugins development / Re: rev-13926 ; ContribPlugins_wx32-unix.workspace

« Last post by LETARTARE on July 29, 2026, 05:14:55 pm »

Thanks.
This effectively removes the warning.

77

Plugins development / Re: rev-13926 ; ContribPlugins_wx32-unix.workspace

« Last post by Miguel Gimenez on July 29, 2026, 04:53:11 pm »

This section in debugger_gdbmi_wx32-unix.cbp looks out of place:

Code

<Extensions>
			<envvars set="cb_plugin" />
			<wxsmith version="1">
				<gui name="wxWidgets" src="" main="" init_handlers="necessary" language="CPP" />
				<resources>
					<wxPanel wxs="wxsmith/config_panel.wxs" src="src/config.cpp" hdr="src/config.h" fwddecl="1" i18n="1" name="ConfigurationPanel" language="CPP" />
				</resources>
			</wxsmith>
		</Extensions>

78

Plugins development / rev-13926 ; ContribPlugins_wx32-unix.workspace

« Last post by LETARTARE on July 29, 2026, 03:23:59 pm »

Context :Leap-15.6, gcc-15.2.0, wx-328, gtk3

Compilation of : ContribPlugins_wx32-unix.workspace => correct

By wanting to reload the default workspace I received this message (attached) , which I could not solve.

I couldn't find anything in 'Envars-wx3.2.x(Unix)'

79

Help / Re: Debugger lldb.exe exits without running target executable

« Last post by Miguel Gimenez on July 29, 2026, 02:55:02 pm »

Debugger finished with status 1

This means the debugger found an error and quit without executing your program at all. C::B expects GDB or CDB as debugger, not LLDB, and it uses commands specific for them that LLDB does not understand. Also, it parses answers using regex that will fail with LLDB.

80

Help / Debugger lldb.exe exits without running target executable

« Last post by MadDavid on July 28, 2026, 10:41:33 pm »

I'm trying to get LLVM CLANG working with Code::Blocks.

I've got basic compilation working, now I'm trying to get debugging working.

So I set up a test project called "TestConsoleDebugger", which has the following code

#include <iostream>
#include <cstdio>

int main()
{
    int iterations = 0;
    FILE* fp;

    while (iterations < 1000000)
    {
      iterations++;
    }

    fp = fopen("Debug.txt", "a+");
    fprintf(fp, "Iterations = %i\n", iterations);
    fflush(fp);
    fclose(fp);
    return 0;
}

and breakpoints on "iteration++;" and "fp = fopen("Debug.txt", "a+");

When I click the red "Debug / Continue" arrow, I get

Active debugger config: GDB/CDB debugger:LLVM 64
Building to ensure sources are up-to-date
Selecting target:
Debug
Adding source dir: E:\Development\TestConsoleDebugger\
Adding source dir: E:\Development\TestConsoleDebugger\
Adding file: E:\Development\TestConsoleDebugger\bin\Debug\TestConsoleDebugger.exe
Changing directory to: E:/Development/TestConsoleDebugger/.
Set variable: PATH=.;E:\Compilers\LLVM\bin;E:\Compilers\LLVM;[bunch of irrelevant paths]E:\Compilers\CodeBlocks;\;E:\Compilers\TDM-GCC-64\bin;E:\Compilers\WinSDK\Windows Performance Toolkit;E:\Compilers\Python310\Scripts;E:\Compilers\Python310;E:\Compilers\CodeBlocks\MinGW\bin;E:\Compilers\VisualStudio\VC\Tools\MSVC\14.31.31103\bin\Hostx64\x64;E:\Compilers\Zip
Starting debugger: E:\Compilers\LLVM\bin\lldb.exe -G -lines -2 -y E:/Development/TestConsoleDebugger/; -srcpath E:/Development/TestConsoleDebugger/; E:/Development/TestConsoleDebugger/bin/Debug/TestConsoleDebugger.exe
done
Debugger finished with status 1
Selecting target:
Debug
Adding source dir: E:\Development\TestConsoleDebugger\
Adding source dir: E:\Development\TestConsoleDebugger\
Adding file: E:\Development\TestConsoleDebugger\bin\Debug\TestConsoleDebugger.exe
Changing directory to: E:/Development/TestConsoleDebugger/.
Set variable: PATH=.;E:\Compilers\LLVM\bin;E:\Compilers\LLVM;[bunch of irrelevant paths]E:\Compilers\CodeBlocks;\;E:\Compilers\TDM-GCC-64\bin;E:\Compilers\WinSDK\Windows Performance Toolkit;E:\Compilers\Python310\Scripts;E:\Compilers\Python310;E:\Compilers\CodeBlocks\MinGW\bin;E:\Compilers\VisualStudio\VC\Tools\MSVC\14.31.31103\bin\Hostx64\x64;E:\Compilers\Zip
Starting debugger: E:\Compilers\LLVM\bin\lldb.exe -G -lines -2 -y E:/Development/TestConsoleDebugger/; -srcpath E:/Development/TestConsoleDebugger/; E:/Development/TestConsoleDebugger/bin/Debug/TestConsoleDebugger.exe
done
Debugger finished with status 1

Code::Blocks does not stop at any breakpoints, the console does not appear, and notably, "Debug.txt" does not appear.  When I click the green "Run" arrow, in contrast, it pops up the console and "Debug.txt" appears in the project directory.

Is there any advice for how to get lldb to actually debug from Code::Blocks?  E.g., do I need to put anything in for "Debugger initialization commands" in the debugger setting?