51
Using Code::Blocks / Re: CB crash today ... but I can continue to use
« Last post by Miguel Gimenez on March 12, 2026, 07:39:21 pm »The issue with the leading comma should be fixed in r13823.
News:
As usual while waiting for the next release - don't forget to check the nightly builds in the forum.
Recent Posts
52
Using Code::Blocks / Re: CB crash today ... but I can continue to use
« Last post by Miguel Gimenez on March 12, 2026, 10:24:53 am »Null pointer dereferencing fixed in r13813, thank you for reporting.
53
Using Code::Blocks / Re: CB crash today ... but I can continue to use
« Last post by blauzahn on March 11, 2026, 09:24:21 pm »When compiling cb (svn13805) with scan-build, its log contains a potential "dereferencing null pointer" in the compiler plugin in file compilerOWgenerator.cpp. See attached screen-shot. Not sure, whether it actually is the reason for the current problem.
for scan-build, see: https://clang.llvm.org/docs/analyzer/user-docs/CommandLineUsage.html#scan-build
Cheers.
for scan-build, see: https://clang.llvm.org/docs/analyzer/user-docs/CommandLineUsage.html#scan-build
Cheers.
54
Using Code::Blocks / Re: CB crash today ... but I can continue to use
« Last post by ThierryD on March 11, 2026, 05:52:31 pm »Sorry, site indicated before is not for source files of Glut32 library, only runtime version of GLUT and Freeglut with MinGW (32 bit) or MSVC (32 bit).
Source files of "glut32" library can be search on https://www.opengl.org/resources/libraries/glut/glut37.zip (in directory \lib\glut\* once unzipped).
Sincerly.
Source files of "glut32" library can be search on https://www.opengl.org/resources/libraries/glut/glut37.zip (in directory \lib\glut\* once unzipped).
Sincerly.
55
Using Code::Blocks / Re: CB crash today ... but I can continue to use
« Last post by ThierryD on March 11, 2026, 02:28:49 pm »Ok, I try to remember my previous actions.
Just to be precise, I use sometimes two screens to have more "surface", principal one of my laptop, secondary two in HDMI mode, but sometimes one screen only (other connected to my old fix PC).
Crash arrived on my laptop (much recent) with two screens, and after choose on "real" target to rebuild and try to use (Open WATCOM compiler), I don't know why but CB signal me that virtual target "glut32" has loose his "asociated" compiler. Just "in aparte", I find strange this mandatory association of compiler into CB to "virtual target", if I use this it's because I want run all build describe into "real target". Maybe, because I don't understand real need of this.
I join CB project in attachement (just add extension .txt to permit loading on forum). Dam that CB forum don't permit directly load of CB project
Source file of "glut32" library can be search on this site : https://www.transmissionzero.co.uk/files/software/development/GLUT/
Sorry, I have not exactly the order of my different actions into CB before crash (I'm just an "normal" user of CB that search to success build ... with many manipulations into IDE).
Regards.
PS : Examine properties of Open WATCM targets into CB project, to understand reason of my others remark in first post.
Just to be precise, I use sometimes two screens to have more "surface", principal one of my laptop, secondary two in HDMI mode, but sometimes one screen only (other connected to my old fix PC).
Crash arrived on my laptop (much recent) with two screens, and after choose on "real" target to rebuild and try to use (Open WATCOM compiler), I don't know why but CB signal me that virtual target "glut32" has loose his "asociated" compiler. Just "in aparte", I find strange this mandatory association of compiler into CB to "virtual target", if I use this it's because I want run all build describe into "real target". Maybe, because I don't understand real need of this.
I join CB project in attachement (just add extension .txt to permit loading on forum). Dam that CB forum don't permit directly load of CB project
Source file of "glut32" library can be search on this site : https://www.transmissionzero.co.uk/files/software/development/GLUT/
Sorry, I have not exactly the order of my different actions into CB before crash (I'm just an "normal" user of CB that search to success build ... with many manipulations into IDE).
Regards.
PS : Examine properties of Open WATCM targets into CB project, to understand reason of my others remark in first post.
56
Using Code::Blocks / Re: CB crash today ... but I can continue to use
« Last post by ollydbg on March 11, 2026, 02:06:16 am »Code
Error occurred on Sunday, March 8, 2026 at 15:29:32.
codeblocks.exe caused an Access Violation at location 00007FF9CC5D0A9F in module compiler.dll Reading from location 0000000000000000.
AddrPC Params
00007FF9CC5D0A9F 000001DD85FC1FC0 000000036CBFE950 00000000FFFFFFFF compiler.dll!0x50a9f
00007FF9CC5C965B 000001DD85FC1FC0 000001DD877C4DE8 000001DD877C4868 compiler.dll!0x4965b
00007FF9CC5D7C4C 000001DD85FC1FC0 000000036CBFD2D0 0000000080000000 compiler.dll!0x57c4c
From your crash report file, I see it looks like the crash happens in the compiler plugin dll.
But from your description, it is hard to understand what are the steps to reproduce this crash. At which stage it get crashed?
Thanks.
57
Using Code::Blocks / CB crash today ... but I can continue to use
« Last post by ThierryD on March 08, 2026, 05:14:45 pm »Hi,
Just a crash during my use of CB today (in attachment).
My usual config : W11 25H2 64 bit.
My DLL project use "many" (very many ...) compilers C/C++ (free or "personal use only") : try to recompile "glut32" library.
Since crash, during load of my workspace, I must had to attribute an "default" compiler at the high level structure of my project CB (named "glut32") because I use "virtual target" to link all of my "real" target (like usual)
I add another "strange" behaviour of CB during use of Open WATCOM compiler V2:
- all compiling steps are succeeded, but
- final linkage fail od DLL fail because list of object files (many ...) begin with first ","
Here detail of command line of linking generate by CB with use of this compiler :
I correct this command line with suppress simply first "," after option "file".... Possible to correct this ?
Last information about use of CB with this compiler, I select into CB project the generation of "import librray" during linkage, but nothing "option" appear during linkage (proof in prvious code inserted).
Option to add to generate import library with this compiler is "option implib=xxxxxxxx" during step of link (xxxxxxxx = name of "target" import library with dirctories if needed).
Possible to add into CB syntax or not ?
Thank's for all.
Thierry D.
Just a crash during my use of CB today (in attachment).
My usual config : W11 25H2 64 bit.
My DLL project use "many" (very many ...) compilers C/C++ (free or "personal use only") : try to recompile "glut32" library.
Since crash, during load of my workspace, I must had to attribute an "default" compiler at the high level structure of my project CB (named "glut32") because I use "virtual target" to link all of my "real" target (like usual
)I add another "strange" behaviour of CB during use of Open WATCOM compiler V2:
- all compiling steps are succeeded, but
- final linkage fail od DLL fail because list of object files (many ...) begin with first ","
Here detail of command line of linking generate by CB with use of this compiler :
Code
wlink.exe option quiet system nt_dll LIBP C:\watcom\lib386\nt;C:\watcom\lib386 name binOW64\Release\glut32.dll library glut32,glu32,opengl32,advapi32,comdlg32,gdi32,winmm file ,objOW64\Release\lib\glut\glut_8x13.obj,objOW64\Release\lib\glut\glut_9x15.obj,objOW64\Release\lib\glut\glut_bitmap.obj,objOW64\Release\lib\glut\glut_bwidth.obj,objOW64\Release\lib\glut\glut_cindex.obj,objOW64\Release\lib\glut\glut_cmap.obj,objOW64\Release\lib\glut\glut_cursor.obj,objOW64\Release\lib\glut\glut_dials.obj,objOW64\Release\lib\glut\glut_dstr.obj,objOW64\Release\lib\glut\glut_event.obj,objOW64\Release\lib\glut\glut_ext.obj,objOW64\Release\lib\glut\glut_fcb.obj,objOW64\Release\lib\glut\glut_fullscrn.obj,objOW64\Release\lib\glut\glut_gamemode.obj,objOW64\Release\lib\glut\glut_get.obj,objOW64\Release\lib\glut\glut_glxext.obj,objOW64\Release\lib\glut\glut_hel10.obj,objOW64\Release\lib\glut\glut_hel12.obj,objOW64\Release\lib\glut\glut_hel18.obj,objOW64\Release\lib\glut\glut_init.obj,objOW64\Release\lib\glut\glut_input.obj,objOW64\Release\lib\glut\glut_joy.obj,objOW64\Release\lib\glut\glut_key.obj,objOW64\Release\lib\glut\glut_keyctrl.obj,objOW64\Release\lib\glut\glut_keyup.obj,objOW64\Release\lib\glut\glut_mesa.obj,objOW64\Release\lib\glut\glut_modifier.obj,objOW64\Release\lib\glut\glut_mroman.obj,objOW64\Release\lib\glut\glut_overlay.obj,objOW64\Release\lib\glut\glut_roman.obj,objOW64\Release\lib\glut\glut_shapes.obj,objOW64\Release\lib\glut\glut_space.obj,objOW64\Release\lib\glut\glut_stroke.obj,objOW64\Release\lib\glut\glut_swap.obj,objOW64\Release\lib\glut\glut_swidth.obj,objOW64\Release\lib\glut\glut_tablet.obj,objOW64\Release\lib\glut\glut_teapot.obj,objOW64\Release\lib\glut\glut_tr10.obj,objOW64\Release\lib\glut\glut_tr24.obj,objOW64\Release\lib\glut\glut_util.obj,objOW64\Release\lib\glut\glut_vidresize.obj,objOW64\Release\lib\glut\glut_warp.obj,objOW64\Release\lib\glut\glut_win.obj,objOW64\Release\lib\glut\glut_winmisc.obj,objOW64\Release\lib\glut\win32_glx.obj,objOW64\Release\lib\glut\win32_menu.obj,objOW64\Release\lib\glut\win32_util.obj,objOW64\Release\lib\glut\win32_winproc.obj,objOW64\Release\lib\glut\win32_x11.obj
Error! E3033: directive error near 'file'
I correct this command line with suppress simply first "," after option "file".... Possible to correct this ?
Last information about use of CB with this compiler, I select into CB project the generation of "import librray" during linkage, but nothing "option" appear during linkage (proof in prvious code inserted).
Option to add to generate import library with this compiler is "option implib=xxxxxxxx" during step of link (xxxxxxxx = name of "target" import library with dirctories if needed).
Possible to add into CB syntax or not ?
Thank's for all.
Thierry D.
58
General (but related to Code::Blocks) / Re: Display resolution issue
« Last post by Miguel Gimenez on March 07, 2026, 10:47:15 am »The quickest solution is adding libonecore.a to the linker.
59
General (but related to Code::Blocks) / Re: Display resolution issue
« Last post by ollydbg on March 07, 2026, 07:56:37 am »AI helps:
I can compile and run the program under msys2/mingw64/gcc.
Code
#include <windows.h>
#include <iostream>
typedef HRESULT (WINAPI *GetIntegratedDisplaySize_t)(double*);
int main()
{
HMODULE hKernelBase = LoadLibraryW(L"kernelbase.dll");
if (!hKernelBase)
{
std::wcout << L"Failed to load kernelbase.dll\n";
return 1;
}
auto GetIntegratedDisplaySize =
(GetIntegratedDisplaySize_t)GetProcAddress(
hKernelBase,
"GetIntegratedDisplaySize"
);
if (!GetIntegratedDisplaySize)
{
std::wcout << L"API not available\n";
return 1;
}
double size = 0.0;
HRESULT hr = GetIntegratedDisplaySize(&size);
if (SUCCEEDED(hr))
{
std::wcout << L"Integrated display size: "
<< size
<< L" inches\n";
}
FreeLibrary(hKernelBase);
}
I can compile and run the program under msys2/mingw64/gcc.
60
Nightly builds / Re: The 09 February 2026 build (13785) is out.
« Last post by ollydbg on March 07, 2026, 07:48:32 am »Hi Xaviou, never mind. I really appreciate all your contributions to wxWidgets and Code::Blocks.