31
Using Code::Blocks / Re: Dark blue text on 'Start here' page hard to read on black background
« Last post by lin_lcs on March 19, 2026, 10:56:02 am »It works. Thank you!
News:
Accounts with zero posts and zero activity during the last months will be deleted periodically to fight SPAM!
Recent Posts
32
General (but related to Code::Blocks) / Re: Valgrind and Cachegrind
« Last post by Evan on March 19, 2026, 10:52:20 am »Thanks.
33
Using Code::Blocks / Re: Dark blue text on 'Start here' page hard to read on black background
« Last post by danselmi on March 19, 2026, 09:38:00 am »Settings -> Environment ... -> Colours -> "Start here page: Link colour"
34
Using Code::Blocks / Dark blue text on 'Start here' page hard to read on black background
« Last post by lin_lcs on March 19, 2026, 07:07:15 am »The startup page "Start here" displays dark blue text on a black background, which is difficult to read. Is it possible to change the font color? 
Code::Blocks: svn 18326
wxWidgets: 3.3.2
Code::Blocks: svn 18326
wxWidgets: 3.3.2
35
General (but related to Code::Blocks) / Re: Valgrind and Cachegrind
« Last post by Miguel Gimenez on March 17, 2026, 11:58:57 am »Quote
==33537== (see section Limitations in user manual)
Quote
On Linux, Valgrind determines at startup the size of the 'brk segment' using the RLIMIT_DATA rlim_cur, with a minimum of 1 MB and a maximum of 8 MB. Valgrind outputs a message each time a program tries to extend the brk segment beyond the size determined at startup. Most programs will work properly with this limit, typically by switching to the use of mmap to get more memory. If your program really needs a big brk segment, you must change the 8 MB hardcoded limit and recompile Valgrind.
The segment is trying to grow to 72 MB, far higher than the 8 MB limit. If you are using malloc() to allocate memory you can ignore this message.
36
Using Code::Blocks / Re: CB crash today ... but I can continue to use
« Last post by ThierryD on March 16, 2026, 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.
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.
37
Using Code::Blocks / Re: Lexer for C only?
« Last post by christo on March 15, 2026, 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.
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.
38
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)
39
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?
Did you find any solution?
40
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?
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?