Recent Posts

1

General (but related to Code::Blocks) / Re: Compilation error using wxWidgets 3.3.3

« Last post by everSome on Today at 12:07:41 am »

FWIW, I get the following stack trace on starting Code::Blocks r13908 in an MSYS2 UCRT64 environment compiled with g++ 16.1 for the assert "page must be a child of the notebook"

#0 0x7ffb856b0c31   wxAuiNotebook::InsertPage(this=0x318d1c0, page_idx=2, page=0x7a7a5c0, caption=..., select=false, bitmap=...) (C:\msys64\home\NateJoe\wxWidgets\wxRegEx_changes\NewConfig\wxWidgets-3.3.3\src\aui\auibook.cpp:2335)
#1 0x7ffb856b0a4c   wxAuiNotebook::AddPage(this=0x318d1c0, page=0x7a7a5c0, caption=..., select=false, bitmap=...) (C:\msys64\home\NateJoe\wxWidgets\wxRegEx_changes\NewConfig\wxWidgets-3.3.3\src\aui\auibook.cpp:2321)
#2 0x7ffb6f688960   cbAuiNotebook::AddPage(this=0x318d1c0, page=0x7a7a5c0, caption=..., select=false, bitmap=...) (C:\msys64\home\NateJoe\CodeBlocks\codeblocks-code-r13908-trunk\src\sdk\cbauibook.cpp:516)
#3 0x7ffb404c84c7   FileManagerPlugin::OnAttach(this=0x6bb3330) (C:\msys64\home\NateJoe\CodeBlocks\codeblocks-code-r13908-trunk\src\plugins\contrib\FileManager\FileManager.cpp:45)
#4 0x7ffb6f6a3267   cbPlugin::Attach(this=0x6bb3330) (C:\msys64\home\NateJoe\CodeBlocks\codeblocks-code-r13908-trunk\src\sdk\cbplugin.cpp:73)
#5 0x7ffb6f75643d   PluginManager::AttachPlugin(this=0x6594b90, plugin=0x6bb3330, ignoreSafeMode=false) (C:\msys64\home\NateJoe\CodeBlocks\codeblocks-code-r13908-trunk\src\sdk\pluginmanager.cpp:203)
#6 0x7ffb6f75c986   PluginManager::LoadAllPlugins(this=0x6594b90) (C:\msys64\home\NateJoe\CodeBlocks\codeblocks-code-r13908-trunk\src\sdk\pluginmanager.cpp:1202)
#7 0x7ff6bdf14b30   MainFrame::ScanForPlugins(this=0x2f771e0) (C:\msys64\home\NateJoe\CodeBlocks\codeblocks-code-r13908-trunk\src\src\main.cpp:1507)
#8 0x7ff6bdf0d291   MainFrame::MainFrame(this=0x2f771e0, parent=0x0) (C:\msys64\home\NateJoe\CodeBlocks\codeblocks-code-r13908-trunk\src\src\main.cpp:794)
#9 0x7ff6bdeb39b2   CodeBlocksApp::InitFrame(this=0x7fa880) (C:\msys64\home\NateJoe\CodeBlocks\codeblocks-code-r13908-trunk\src\src\app.cpp:571)
#10 0x7ff6bdeb5450   CodeBlocksApp::OnInit(this=0x7fa880) (C:\msys64\home\NateJoe\CodeBlocks\codeblocks-code-r13908-trunk\src\src\app.cpp:810)
#11 0x7ff6bdfb6655   wxAppConsoleBase::CallOnInit(this=0x7fa880) (C:\msys64\home\NateJoe\wxWidgets\wxRegEx_changes\NewConfig\wxWidgets-3.3.3\include\wx\app.h:92)
#12 0x7ffb851f07bc   operator() (__closure=0x5ffda7) (C:\msys64\home\NateJoe\wxWidgets\wxRegEx_changes\NewConfig\wxWidgets-3.3.3\src\common\init.cpp:553)
#13 0x7ffb851f0b2f   wxSafeCall<int, wxEntryReal(int&, wxChar**)::<lambda()>, wxEntryReal(int&, wxChar**)::<lambda()> >(const struct {...} &, const struct {...} &)(func=..., handler=...) (C:\msys64\home\NateJoe\wxWidgets\wxRegEx_changes\NewConfig\wxWidgets-3.3.3\include\wx\private\safecall.h:40)
#14 0x7ffb851f0995   wxEntryReal(argc=@0x7ffb86621ea0: 9, argv=0x7fbcb0) (C:\msys64\home\NateJoe\wxWidgets\wxRegEx_changes\NewConfig\wxWidgets-3.3.3\src\common\init.cpp:550)
#15 0x7ffb85288c00   wxEntry(argc=@0x7ffb86621ea0: 9, argv=0x7fbcb0) (C:\msys64\home\NateJoe\wxWidgets\wxRegEx_changes\NewConfig\wxWidgets-3.3.3\src\msw\main.cpp:175)
#16 0x7ffb85288cf0   wxEntry(hInstance=0x7ff6bdeb0000, nCmdShow=10) (C:\msys64\home\NateJoe\wxWidgets\wxRegEx_changes\NewConfig\wxWidgets-3.3.3\src\msw\main.cpp:226)
#17 0x7ff6bdeb2c73   WinMain(hInstance=0x7ff6bdeb0000, hPrevInstance=0x0, lpCmdLine=0x724cbf "--debug-log --no-dde --no-check-associations --multiple-instance --no-splash-screen --verbose -p debug", nCmdShow=10) (C:\msys64\home\NateJoe\CodeBlocks\codeblocks-code-r13908-trunk\src\src\app.cpp:381)
#18 0x7ff6be02d05a   main(argc=<optimized out>, argv=<optimized out>, envp=<optimized out>) (D:/W/B/src/mingw-w64/mingw-w64-crt/crt/crtexewin.c:62)
#19 0x7ff6bdeb115a   __tmainCRTStartup() (D:/W/B/src/mingw-w64/mingw-w64-crt/crt/crtexe.c:265)
#20 0x7ffc042e7374   KERNEL32!BaseThreadInitThunk() (C:\WINDOWS\System32\kernel32.dll:??)
#21 0x7ffc04f1cc91   ntdll!RtlUserThreadStart() (C:\WINDOWS\SYSTEM32\ntdll.dll:??)
#22 ??   ?? () (??:??)

2

Help / Re: Debug Report popup message then crash

« Last post by Miguel Gimenez on Yesterday at 01:18:52 pm »

Reincident stupid spammer (with another name) reported to moderator.

3

Help / Re: Debug Report popup message then crash

« Last post by jacksonmark on Yesterday at 11:38:33 am »

Hello,

I am using code::blocks on Mac and I'm programming a game in SFML. There is several specific cases where a popup appears like in the screenshot attached and freezes my program. Pressing Ok or Cancel does nothing but crash code::blocks. One way to make the popup appear is by writing Texture backgroundTexture; followed by backgroundTexture.loadFromFile - and then it freezes - before I can write the full
backgroundTexture.loadFromFile("graphics/background.png");. The other way I can make the "debug report" appear is by pressing Settings > Scripting, and again, same thing. I have code completion turned off because otherwise grey squares appear instead of actual code completion (Seems to be a Mac issue).

I have read other people's reports where this has happened and have tried to both rename and remove cbKeyBinder10.ini, cbKeyBinder10.ini.bak, and default.conf inside ~/Library/Application Support/codeblocks/slope game 2 and no change has worked. Whatever I do to them is insignificant because they are remade again if the program starts without them and my changes remain there with no success.

If anyone knows how I could fix this issue (because I literally cannot move forward), I would gladly appreciate it.

Thanks

Here are a few suggestions to help you resolve the problem:

Update Code::Blocks: Ensure you are using the latest version, as updates often fix bugs.

Check SFML Setup: Verify that SFML is correctly installed and configured in Code::Blocks.

Run from Terminal: Try compiling and running your code directly from the Terminal to see if you get more detailed error messages.

Disable Scripting: If you don't need the scripting feature, consider disabling it to prevent unwanted popups.

Reset Configuration: Try deleting the entire configuration folder in ~/Library/Application Support/codeblocks to create fresh configuration files.

Check Permissions: Ensure Code::Blocks has the necessary permissions to read and write files.

Hopefully, one of these solutions will help you move forward. Good luck!

4

Using Code::Blocks / Re: Project dependent upon another project?

« Last post by Miguel Gimenez on Yesterday at 11:07:17 am »

Stupid spammer jacksonjame reported to moderator.

5

Using Code::Blocks / Re: Project dependent upon another project?

« Last post by jacksonjame on Yesterday at 10:29:03 am »

I did this regularly with MSVS 2005, but have not messed with it in ages. I am building a cross-platform utility that will allow users to backup saves/config/etc from any game whether they are on Windows or Linux. This will consist of two separate projects. Both must build for the complete solution.

One is a service that monitors for specified programs to be run and backs up their data when they start (you start game A, it sees this, and backs up whatever the user specified). This is literally a Windows service that has no UI and will be the same under Linux.

The other is a wxWidgets project that will provide a UI to specify games (executables) and what to backup for each game. This simply writes a configuration file that the service reads when it starts or when it restarts. This is crucial for making the project easy enough for non-techs to use.

The master project will build each of the child projects and (if possible) package the outputs of said projects into an installer or tgz for users to install. The master project will not have any actual code to build. It just builds the two child projects and then builds the installer.

How can I accomplish this? Also, would it be possible to somehow tie this entire thing to my stickman hook Github so it lives there and I can allow others access to the code?

Creating a cross-platform utility for backing up game data is a fantastic idea, especially for non-tech users. For the build process, consider using CMake as your build system, as it works well with both Windows and Linux and can handle multiple projects. You can set up the master project to call the build commands for the child projects and package them into an installer or tarball.
As for integrating with GitHub, you can create a repository for your project and push your code there. This will allow others to contribute and access your work easily.

6

Development / Re: Lost early documentation

« Last post by Miguel Gimenez on July 14, 2026, 12:37:32 pm »

Another spammer reported to moderator.

7

Development / Re: Lost early documentation

« Last post by eaglesky on July 14, 2026, 10:33:04 am »

You need document in In such category Category:Developer Documentation - Code::Block Blast?

It would be great if more detailed guides and examples were available for new developers joining the project.

8

Development / Re: Lost early documentation

« Last post by Miguel Gimenez on July 13, 2026, 12:59:14 pm »

Another spammer reported to moderator.

9

Development / Re: Lost early documentation

« Last post by ChelsWhittaker on July 13, 2026, 11:48:59 am »

That's really relatable! I've spent countless hours diving into old systems and documentation, only to lose a crucial link. It's a frustrating but common experience when you're trying to piece together legacy information. Good luck finding it! Geometry Dash

10

Using Code::Blocks / Re: Can't Get Debugger to Work

« Last post by Miguel Gimenez on July 13, 2026, 11:27:20 am »

Profile and normal spammers reported to moderator.