1
General (but related to Code::Blocks) / Re: Valgrind and Cachegrind
« Last post by Miguel Gimenez on Today at 05:10:50 am »Spam reported to moderator.
News:
As usual while waiting for the next release - don't forget to check the nightly builds in the forum.
Recent Posts
2
General (but related to Code::Blocks) / Re: Valgrind and Cachegrind
« Last post by sikasema on Today at 04:12:05 am »The segment is attempting to expand to 72 MB, which exceeds the 8 MB limit. If the memory allocation is being handled with malloc(), this warning can be safely ignored.
geometry dash lite
geometry dash lite
3
Development / Re: CVE-2020-37121 - buffer overflow exploit
« Last post by Miguel Gimenez on Yesterday at 01:57:57 pm »Delayed profile spammer reported to moderator.
4
Help / Re: Cannot find the compiler
« Last post by Miguel Gimenez on Yesterday at 01:57:17 pm »Spam reported to moderator.
6
Development / Re: CVE-2020-37121 - buffer overflow exploit
« Last post by sumoreh8841 on May 14, 2026, 11:43:24 am »From the NVD description it looks like a generic SEH-based buffer overflow pattern rather than something specific to Code::Blocks itself. Has anyone checked whether this CVE is tied to a bundled third-party library rather than the IDE core?
7
Using Code::Blocks / How prevent unfold code at closed brackets.
« Last post by squad on May 09, 2026, 11:54:54 am »It's a great IDE. Thanks. 
There's some folded code.
When I'm adding code before that folded section and accidentally type an right bracket(no left bracket, not closed.), all the folded code that follows gets expanded.
Is there any way to prevent this?
There's some folded code.
When I'm adding code before that folded section and accidentally type an right bracket(no left bracket, not closed.), all the folded code that follows gets expanded.
Is there any way to prevent this?
8
General (but related to Code::Blocks) / Re: Welcome Newcomers - PLEASE READ!!!
« Last post by squad on May 09, 2026, 11:47:08 am »I am new, I am here. I am a human 
9
Help / Re: debugger_gdbmi
« Last post by Pecan on May 08, 2026, 04:28:25 pm »Great work Pecan. Or in my words bloody good job (OZ).
One thing to remember is that testing is a killer and needs to be done using it against CB to fix bugs. It's a PITA an takes time.
The second thing to remember is no matter how good you think the debugger is there WILL be bugs slip through the corner cases or the homer effect (doh i did not check that or think to check that).
Overall I think in the short term this should go into the CB mainline to replace the existing GDB debugger as the existing GDB debugger uses the ancient and technically obsolete I/F.
But in the long term ..... move to the next one and save yourself the pain, unless ....... . At the end only you know the best way forward for yourself.
Good luck and keep up the great work.
Thanks. I'm already working inside your DAP prototype.
It's a bitch. I hate that awful JSON parser.
I still don't understand what I have to do to define those To: and From: entries.
Praying to the code gods just does not work.
Even Gemini and Claude get confused and get it wrong.
But if I just try first (and always get it wrong) the robots can see how to fix it.
10
Help / Re: debugger_gdbmi
« Last post by AndrewCot on May 08, 2026, 01:11:30 pm »Great work Pecan. Or in my words bloody good job (OZ).
One thing to remember is that testing is a killer and needs to be done using it against CB to fix bugs. It's a PITA an takes time.
The second thing to remember is no matter how good you think the debugger is there WILL be bugs slip through the corner cases or the homer effect (doh i did not check that or think to check that).
Overall I think in the short term this should go into the CB mainline to replace the existing GDB debugger as the existing GDB debugger uses the ancient and technically obsolete I/F.
But in the long term ..... move to the next one and save yourself the pain, unless ....... . At the end only you know the best way forward for yourself.
Good luck and keep up the great work.
One thing to remember is that testing is a killer and needs to be done using it against CB to fix bugs. It's a PITA an takes time.
The second thing to remember is no matter how good you think the debugger is there WILL be bugs slip through the corner cases or the homer effect (doh i did not check that or think to check that).
Overall I think in the short term this should go into the CB mainline to replace the existing GDB debugger as the existing GDB debugger uses the ancient and technically obsolete I/F.
But in the long term ..... move to the next one and save yourself the pain, unless ....... . At the end only you know the best way forward for yourself.
Good luck and keep up the great work.