Recent Posts

51

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.

52

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 :

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.


 

53

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.

54

General (but related to Code::Blocks) / Re: Display resolution issue

« Last post by ollydbg on March 07, 2026, 07:56:37 am »

AI helps:

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.

55

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.

56

General (but related to Code::Blocks) / Re: Display resolution issue

« Last post by JoeH on March 07, 2026, 04:19:55 am »

I gave the recommended "Get" function a try.  Even though I included the sysinfoapi.h file in the main header file, the code will not compile successfully.  I get a error stating "GetIntegratedDisplaySize was not declared in this scope".

Joe

57

Nightly builds / Re: The 06 March 2026 build (13810) is out.

« Last post by Xaviou on March 06, 2026, 08:37:10 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'

58

Nightly builds / The 06 March 2026 build (13810) is out.

« Last post by killerbot on March 06, 2026, 02:47:23 pm »

We switched to gcc 15.1.0 (on 23 May 2025) --> download the new wx/mingw dll's see link below

Get the compiler we use here : https://github.com/brechtsanders/winlibs_mingw/releases/download/15.1.0posix-12.0.0-ucrt-r1/winlibs-x86_64-posix-seh-gcc-15.1.0-mingw-w64ucrt-12.0.0-r1.7z

Get quick announcements through the RSS feed http://www.codeblocks.org/nightly/CodeBlock_RSS.xml

Before you use a nightly make sure you understand how it works.

A link to the unicode windows wxWidget dll(s) for Code::Blocks : https://sourceforge.net/projects/codeblocks/files/Binaries/Nightlies/Prerequisites/wxmsw32u_gcc_cb_wx328_2D_gcc1510-mingw64.7z
A link to Mingw64 dll's needed by Code::Blocks : http://sourceforge.net/projects/codeblocks/files/Binaries/Nightlies/Prerequisites/Mingw64dlls15.1.0.7z


The 06 March 2026 build is out.
  - Windows :
   http://sourceforge.net/projects/codeblocks/files/Binaries/Nightlies/2026/CB_20260306_rev13810_win64.7z
  - Linux :
   none

The current SDK version is : 2.25.0

Resolved Fixed:

• lcbp: add the unified CodeBlocks cbps for Windows OS. (thanks gd_on)

Regressions/Confirmed/Annoying/Common bugs:

59

Nightly builds / Re: The 09 February 2026 build (13785) is out.

« Last post by Xaviou on March 06, 2026, 10:05:55 am »

Hi

Hi, Xaviou, I'm not sure why the "at" is preferred instead of "[]"?

Well, I don't either really know  It's a solution given by chatgpt to solve this building problem:

ArrayChecks is a wxArrayBool, and with GCC 15, the non-const [] operator of wxBaseArray<bool> breaks (bool& is impossible with vector<bool>)

We have some discussion here: New wxWidgets releases

I apologize : I had this solution just after rev13802 (solving the first building problem).
I updated to rev 13810 before creating the patch, and tested the build, but only with the patch, not without.

Now that I have tested the rev 13810 "as is", I can confirm it works without the watch.
Again, sorry.

Regards.
Xav'

60

Nightly builds / Re: The 09 February 2026 build (13785) is out.

« Last post by ollydbg on March 06, 2026, 12:55:34 am »

Hi.

There is also some few code modifications to the wxSmith plugin for wxWidgets-3.3.2.

Attached is a patch  from svn 13810.

Regards
Xav'

Hi, Xaviou, I'm not sure why the "at" is preferred instead of "[]"?

We have some discussion here: New wxWidgets releases

Thanks.