1
Help / Re: Build error "'HEAP_INFORMATION_CLASS' has not been declared"
« Last post by Miguel Gimenez on Today at 07:58:06 am »Spam reported to moderator.
News:
When registered with our forums, feel free to send a "here I am" post here to differ human beings from SPAM bots.
Recent Posts
2
General (but related to Code::Blocks) / File Association?
« Last post by skrath on Today at 04:10:10 am »When one .c file is open in CodeBlocks, I am not able to open another .c file from the Windows Explorer (by double clicking on it) in a 2nd tab in the CodeBlocks IDE.
If I double click on the file, the simply CodeBlocks IDE comes into focus without opening the file.
In my Environment setting, I have multi-instances checked out; open in the same instance checked in.
Can anybody suggest a solution?
If I double click on the file, the simply CodeBlocks IDE comes into focus without opening the file.
In my Environment setting, I have multi-instances checked out; open in the same instance checked in.
Can anybody suggest a solution?
3
Help / Re: Build error "'HEAP_INFORMATION_CLASS' has not been declared"
« Last post by beautylesson on Today at 04:05:12 am »You likely have a broken Compiler or wxWidgets installation or do NOT have WX_PRECOMP defined (but the log you posted has it defined).Maybe I need to post this question in another forum topic? For example, in Using Code::Blocks? I really need to configure Code::Blocks to create GTK applications, and in this topic the answer is no.
Where and How did you do the wxWidgets installation?
It appears to be missing the #include "wx/msw/wrapwin.h" from "wx/wxprec.h" header.
(The wrapwin.h includes windows.h; that includes winnt.h that defines HEAP_INFORMATION_CLASS fnf)
In the app.cpp file try adding the code below between the including <sdk.h> and "app.h".
If it works; likely have wxWidgets issue; if it still fails likely has a bad Compiler.
To confirm compiler try including
#include <windows.h>
or
#include <winnt.h>
Edit 4 or 5: changed __WINDOWS__ to __WXMSW__ in code below.Code#include <sdk.h>
#ifndef WX_PRECOMP
#ifdef __WXMSW__
#include <wx/msw/wrapwin.h> // HEAP_INFORMATION_CLASS
#endif // __WXMSW__
#endif // WX_PRECOMP
#include "app.h"
Tim S.
4
General (but related to Code::Blocks) / Re: File Association?
« Last post by skrath on Yesterday at 06:09:24 pm »I am not able to open a .c file from Windows Explorer in a second tab, when one .c file is open in IDE. By double clicking on the file icon in Explorer, one IDE comes into focus without actually opening the file.
Can anybody suggest a solution?
Can anybody suggest a solution?
5
General (but related to Code::Blocks) / Re: Welcome Newcomers - PLEASE READ!!!
« Last post by skrath on Yesterday at 06:00:45 pm »I am new, I am here.
6
Using Code::Blocks / Re: Dark blue text on 'Start here' page hard to read on black background
« Last post by lin_lcs on Yesterday at 10:56:02 am »It works. Thank you!
7
General (but related to Code::Blocks) / Re: Valgrind and Cachegrind
« Last post by Evan on Yesterday at 10:52:20 am »Thanks.
8
Using Code::Blocks / Re: Dark blue text on 'Start here' page hard to read on black background
« Last post by danselmi on Yesterday at 09:38:00 am »Settings -> Environment ... -> Colours -> "Start here page: Link colour"
9
Using Code::Blocks / Dark blue text on 'Start here' page hard to read on black background
« Last post by lin_lcs on Yesterday at 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
10
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.