Recent Posts

1

Using Code::Blocks / Re: CB crash today ... but I can continue to use

« Last post by ThierryD on Today at 05:39:02 pm »

Thank's to CB Team.

Anomaly corrected (apart "option IMPLIB=xxx", but I can add in another options in linker TAB). It's alright.

You can close this topic.

Regards.

2

Using Code::Blocks / Re: Lexer for C only?

« Last post by christo on Yesterday at 06:45:39 pm »

For C coders, patch https://github.com/josephch/codeblocks/commit/c44cbfaeb666a3eb205dc23bae547c7db849d879.patch can be used.

It cannot be used for those who code in C++ as lexer is applied based on extensions and .h can have only one type of lexer. Extension .h supporting C and C++ based on project  would be a nice feature.

3

Using Code::Blocks / Re: Lexer for C only?

« Last post by Hyena on March 14, 2026, 08:13:23 pm »

I'm also a C coder.

Did you find any solution?

Kind of. I started using KDevelop and constructed a custom color theme for it using the colors from Code::Blocks. You can get it from here:
https://github.com/1Hyena/kdevelop-theme

KDevelop is actually good IDE for large projects (more then 50k lines of code)

4

Using Code::Blocks / Re: Lexer for C only?

« Last post by Evan on March 14, 2026, 07:54:26 pm »

I'm also a C coder.

Did you find any solution?

5

General (but related to Code::Blocks) / Valgrind and Cachegrind

« Last post by Evan on March 14, 2026, 03:18:53 pm »

I'm testing my C99 code, that seems to run as intended and I'm using valgrind-3.22.0. on Linux Mint 22.3 and Code::Blocks  Build: 2024-03-31
command: valgrind  --leak-check=full --track-origins=yes --xml=yes

-------------- Application output --------------

I hope that means no memory leaks and my System Monitor is not showing any leaks/peaks.


Cachegrind however gives a message: brk segment overflow in thread #1: can't grow to 0x4856000
valgrind --version
valgrind-3.22.0
valgrind  --tool=cachegrind "/home/C/Test/bin/Debug/Test"
==33537== Cachegrind, a high-precision tracing profiler
==33537== Copyright (C) 2002-2017, and GNU GPL'd, by Nicholas Nethercote et al.
==33537== Using Valgrind-3.22.0 and LibVEX; rerun with -h for copyright info
==33537== Command: /home/C/Test/bin/Debug/Kalechen
==33537==
==33537== brk segment overflow in thread #1: can't grow to 0x4856000
==33537== (see section Limitations in user manual)
==33537== NOTE: further instances of this message will not be shown
==33537==
==33537== I refs:        5,078,382,897

Any help is appreciated?

6

Using Code::Blocks / Re: CB crash today ... but I can continue to use

« Last post by Miguel Gimenez on March 14, 2026, 11:49:29 am »

The tabs were already there, but they were mixed with spaces so I unified them.

7

Using Code::Blocks / Re: CB crash today ... but I can continue to use

« Last post by blauzahn on March 14, 2026, 09:35:24 am »

Thank you for applying the patch. Sorry for the tabs.

8

Nightly builds / Re: The 12 March 2026 build (13823) is out.

« Last post by Xaviou on March 13, 2026, 04:51:26 pm »

Hi.

32 bits version for Windows (and also 64 bits version) can be downloaded from my website.
I made both a wxWidgets-3.2.10 and wxWidgets-3.3.2 linked versions

Debian Trixie (64 bits) and Bookworm (32 and 64 bits) can be installed from my repo
The corresponding unsigned deb files can also be downloaded from the website page linked above.

Ubuntu-22.04, 24.10 and 25.10 versions can be installed from my ppa (they are now available for both amd64 and arm64 architectures).

Regards
Xav'

9

Using Code::Blocks / Re: CB crash today ... but I can continue to use

« Last post by Miguel Gimenez on March 13, 2026, 10:08:45 am »

Patch applied in r13824, thank you.

NOTE: I have changed tabs to spaces in both files after applying the patch.

10

Using Code::Blocks / Re: CB crash today ... but I can continue to use

« Last post by blauzahn on March 13, 2026, 06:36:31 am »

patch attached