Recent Posts

Pages: 1 2 3 [4] 5 6 7 8 9 10
31
Using Code::Blocks / Re: Codeblocks 25.03 crashes when I use Hex editor
« Last post by stahta01 on August 23, 2025, 03:11:40 pm »
He is saying that a problem happened using HexEditor on codeblocks.exe; I saw the problem 2 out of 3 times; the problem took about 1 to 2 minutes to crash

codeblocks.RPT

Code
Error occurred on Saturday, August 23, 2025 at 09:09:07.

codeblocks.exe caused an Access Violation at location 00007FFE3A97C209 in module libHexEditor.dll Reading from location 0000000000000000.

AddrPC           Params
00007FFE3A97C209 000001AFC5F26BA0 000001AFCD2B88A0 0000000000000200  libHexEditor.dll!HexEditPanel::ClampCursorToVisibleArea+0x59  [/usr/src/debug/mingw-w64-codeblocks_dm/build-UCRT64/src/plugins/contrib/HexEditor/../../../../../codeblocks-git/src/plugins/contrib/HexEditor/HexEditPanel.cpp @ 1101]
00007FFE3A97ECB0 0000000000BE01FE 0000000000000200 0000000000000000  libHexEditor.dll!HexEditPanel::OnContentMouseWheel+0x44  [/usr/src/debug/mingw-w64-codeblocks_dm/build-UCRT64/src/plugins/contrib/HexEditor/../../../../../codeblocks-git/src/plugins/contrib/HexEditor/HexEditPanel.cpp @ 759]
00007FFE77F83719 0000000001AC075A 00000000000A0476 0000000001AC075A  wxbase332u_gcc_custom.dll!wxAppConsoleBase::CallEventHandler+0xb9
00007FFE780B22B8 000000622EFFF3D0 00007FFEA238C34F 000000622EFFF450  wxbase332u_gcc_custom.dll!wxEvtHandler::ProcessEventIfMatchesId+0x78
00007FFE780B35BD 0000000000000001 000001AFCCEDF100 000000622EFFF3D8  wxbase332u_gcc_custom.dll!wxEvtHandler::SearchDynamicEventTable+0xad
00007FFE780B3A3B 000000622EFFF450 00007FFE77321E25 000001AC0000075A  wxbase332u_gcc_custom.dll!wxEvtHandler::TryHereOnly+0x2b
00007FFE780B3AEA 000000BE000001FE 00000000000000BE 00000000000001FE  wxbase332u_gcc_custom.dll!wxEvtHandler::ProcessEventLocally+0x2a
00007FFE780B3B91 00000000000001FE 000001AC0000075A 0000000000780000  wxbase332u_gcc_custom.dll!wxEvtHandler::ProcessEvent+0x61
00007FFE780B287A 0000000000780000 000001AFCCEDF100 000000BE000001FE  wxbase332u_gcc_custom.dll!wxEvtHandler::SafelyProcessEvent+0x3a
00007FFE773282D7 0000000002000001 00000000000205DE 00007FFE00000000  wxmsw332u_core_gcc_custom.dll!wxWindow::HandleMouseWheel+0xc7
00007FFE7732CDFF 00000000000A0476 00007FFE77324EF8 0000006200000000  wxmsw332u_core_gcc_custom.dll!wxWindow::MSWHandleMessage+0x72f
00007FFE7732E0BE 0000075A00000001 00007FFE77E8F8DE 0000000000000001  wxmsw332u_core_gcc_custom.dll!wxWindow::MSWWindowProc+0x3e
00007FFEA238EF5C 0000000000000000 00007FFE77324EE0 000000622EDC3800  USER32.dll!CallWindowProcW+0x60c
00007FFEA238E684 00007FFE77324EE0 0000000000000000 000000622EFFFB20  USER32.dll!DispatchMessageW+0x4a4
00007FFEA238BC76 0000000000000009 000001AFC5A94CD0 0000000000000000  USER32.dll!IsDialogMessageW+0x326
00007FFE77323F4B 000000622EFFFB20 00007FFE7810DEA0 000001AFCCF0CDE0  wxmsw332u_core_gcc_custom.dll!wxWindow::MSWSafeIsDialogMessage+0x3b
00007FFE77348288 0000000000000000 0000000000000000 0000000000000000  wxmsw332u_core_gcc_custom.dll!wxGUIEventLoop::PreProcessMessage+0xd8
00007FFE773482F6 000001AFCCD882C0 0000000000000000 00007FFE77907240  wxmsw332u_core_gcc_custom.dll!wxGUIEventLoop::ProcessMessage+0x26
00007FFE773480D6 0000000000000000 0000000000010000 000001AFCCF0CDC0  wxmsw332u_core_gcc_custom.dll!wxGUIEventLoop::Dispatch+0xb6
00007FFE77FB3291 00007FF62734C160 0000000000000000 000001AFCC92E900  wxbase332u_gcc_custom.dll!wxEventLoopManual::ProcessEvents+0x31
00007FFE77FB334E 000001AFC5A20580 00007FFEA119FDE6 0000000000000000  wxbase332u_gcc_custom.dll!wxEventLoopManual::DoRunLoop+0x8e
00007FFE77FB3448 0000000000000000 00007FFE772CB88C 0000000000000000  wxbase332u_gcc_custom.dll!wxEventLoopManual::DoRun+0x38
00007FFE77FB3098 000001AFCCF0CDC0 00007FF627321B01 00007FFEA385C9D0  wxbase332u_gcc_custom.dll!wxEventLoopBase::Run+0x58
00007FFE77F84506 000001AFC5A20580 0000000000000001 000001AFC5A94CD0  wxbase332u_gcc_custom.dll!wxAppConsoleBase::MainLoop+0x66
00007FF627278A82 00007FF6273AB6B8 0000000000000001 000001AFC5A94CD0  codeblocks.exe!CodeBlocksApp::OnRun+0x16  [/usr/src/debug/mingw-w64-codeblocks_dm/build-UCRT64/src/src/../../../codeblocks-git/src/src/app.cpp @ 923]
00007FFE77FF46F0 0000000000000430 0000000000000024 0000000000000001  wxbase332u_gcc_custom.dll!wxEntryReal+0xc0
00007FF627272101 00007FFEA1281270 00007FF627313AF0 0000000000000002  codeblocks.exe!WinMain+0xa  [/usr/src/debug/mingw-w64-codeblocks_dm/build-UCRT64/src/src/../../../codeblocks-git/src/src/app.cpp @ 334]
00007FF6272710C9 0000000000000000 0000000000000000 0000000000000000  codeblocks.exe!__tmainCRTStartup+0xb9  [D:/W/B/src/mingw-w64/mingw-w64-crt/crt/crtexe.c @ 236]
00007FF6272713F6 0000000000000000 0000000000000000 0000000000000000  codeblocks.exe!WinMainCRTStartup+0x16  [D:/W/B/src/mingw-w64/mingw-w64-crt/crt/crtexe.c @ 91]
00007FFEA3837374 0000000000000000 0000000000000000 0000000000000000  KERNEL32.DLL!BaseThreadInitThunk+0x14
00007FFEA399CC91 0000000000000000 0000000000000000 0000000000000000  ntdll.dll!RtlUserThreadStart+0x21
32
Using Code::Blocks / Re: Codeblocks 25.03 crashes when I use Hex editor
« Last post by AntonyF on August 23, 2025, 11:28:34 am »
Quote from: Wkerry on August 23, 2025, 05:24:14 am
This is for 25.03 64bit installer codeblocks-25.03-setup.exe (release #2):

If I load cb_console_runner.exe via the "File->Open with hex editor" it works.
If I load codeblocks.exe via the "File->Open with hex editor"   it crashes and burns.

I would like to replicate the test you did on my PCs using:

cb_console_runner.exe

But I don't understand how you loaded the Hex Editor.
Could you kindly post how to do it?

Thank you in advance for your help.

33
Using Code::Blocks / Re: Codeblocks 25.03 crashes when I use Hex editor
« Last post by stahta01 on August 23, 2025, 06:59:55 am »
So, a locked file causes something like the OP issue. The codeblocks exe is likely a locked file.

Tim S.
34
Using Code::Blocks / Re: Codeblocks 25.03 crashes when I use Hex editor
« Last post by Wkerry on August 23, 2025, 05:24:14 am »
This is for 25.03 64bit installer codeblocks-25.03-setup.exe (release #2):

If I load cb_console_runner.exe via the "File->Open with hex editor" it works.
If I load codeblocks.exe via the "File->Open with hex editor"   it crashes and burns.

35
Using Code::Blocks / Re: Codeblocks 25.03 crashes when I use Hex editor
« Last post by AntonyF on August 21, 2025, 11:38:37 pm »
Hello Blauzahn, Hello Miguel,

Thank you for your help.

I can add that I have detected the same issue on a third PC.

So, in total, there are three PCs with the same issue. It should be noted that the three PCs are completely different from each other in terms of hardware.

All PCs have the following things in common:

Operating system:

Windows 10 LTSC 2021

Antivirus:

Eset Internet Security

VPN:

Proton VPN

My first suspicion fell on the antivirus, but I have not yet had confirmation.

As soon as I have some free time, I will run tests on other operating systems, as well as other cross-tests.

I will keep you updated and thank you for everything.

36
Using Code::Blocks / Re: Codeblocks 25.03 crashes when I use Hex editor
« Last post by blauzahn on August 21, 2025, 08:07:51 pm »
Maybe some low hanging fruit before trying to "reproduce" UB: cppcheck reports e.g. several uninitialized variables etc. The results are in its attached report.

The HexEditor plugin looks like it predates C++-11. I just gave it a quick glance. I do not use the plugin myself.

37
Using Code::Blocks / Re: Codeblocks 25.03 crashes when I use Hex editor
« Last post by Miguel Gimenez on August 21, 2025, 03:03:32 pm »
AFAIK the code for the Hex Editor has not changed between releases. To fix this we need a way to reproduce, random crashes are hard to fix; I have not been able to reproduce the issue in my system.

You can post a ticket, of course.
38
Using Code::Blocks / Re: Codeblocks 25.03 crashes when I use Hex editor
« Last post by AntonyF on August 21, 2025, 11:06:07 am »
I ran some tests with the portable version of CodeBlocks 20.03 and the Hex Editor works perfectly.

I exported the Hex Editor from version 20.03 and tried to import it into version 25.03, but obviously it didn't work.

I gather that the problem is inherent in version 25.03. Searching the Internet, I saw that other users have the same problem.

Do you know if it is possible to report this problem?

Maybe someone will be able to solve it.

39
Using Code::Blocks / Re: Codeblocks 25.03 crashes when I use Hex editor
« Last post by AntonyF on August 20, 2025, 11:41:12 pm »
Hi Miguel,
It's not a question of size. The same exe file opens occasionally, and when it works, I can open four or five at the same time without any problems. They are small test programs of varying sizes, but in the range of 60-120 Kbytes.
Then I close and reopen CodeBlocks or restart the PC, and it no longer opens the same files that it used to open without any problems, causing CodeBlocks to crash.
40
General (but related to Code::Blocks) / Observations on using CodeBlocks_wx33_64.cbp and friends
« Last post by everSome on August 20, 2025, 09:23:52 pm »
I've generalized my version of the *_wx33_64.cbp files to the form used in src/CodeBlocks_wx33_64.cbp where in the project wide compiler options begin with
Code
			<Add option="-Wall" />
			<Add option="-m64" />
			<Add option="$(#CB_RELEASE_TYPE)" />
with one caveat. I removed the option
Code
			<Add option="$(#CB_CPP_STD)" />
from all the target compiler option lists and moved it into the Project compiler list so that I now use the combination:
Code
			<Add option="-Wall" />
			<Add option="-m64" />
			<Add option="$(#CB_CPP_STD)" />
			<Add option="$(#CB_RELEASE_TYPE)" />
Doing it this way allows one to define CB_CPP_STD as "-std=gnu17 -std=gnu++20". This works when using a variant of CompilerMINGW as it uses the specifications CFlags and CPPFlags in
Code
src\plugins\compilergcc\resources\compilers\options_common_sort.xml
to determine what is inappropriate for C or C++ compilations.

The current lists therein are sufficient for distinguishing where it is
appropriate to use "-std=gnu17" versus "-std=gnu++20".

Nonetheless, these CFlags and CPPFlags specs could use a minor update. Seems both gcc and clang support the new CFlags, but of the as yet future C++ standard, g++ uses std=c++26 -std=gnu++26 where clang++ uses -std=c++2c -std=gnu++2c
Code
diff -r 332d682e3f78 -r ad163b81827c src/plugins/compilergcc/resources/compilers/options_common_sort.xml
--- a/src/plugins/compilergcc/resources/compilers/options_common_sort.xml       Sat Aug 16 07:44:16 2025 -0700
+++ b/src/plugins/compilergcc/resources/compilers/options_common_sort.xml       Sat Aug 16 07:47:40 2025 -0700
@@ -3,10 +3,10 @@
 <CodeBlocks_compiler_options>
     <Sort CFlags="-std=c89 -std=gnu89 -std=c90 -std=gnu90 -std=iso9899:1990 -std=iso9899:1994
                   -std=c99 -std=gnu99 -std=iso9899:1999 -std=c11 -std=gnu11 -std=iso9899:2011
-                  -std=c17 -std=iso9899:2017"/>
+                  -std=c17 -std=gnu17 -std=iso9899:2017 -std=c23 -std=gnu23 -std=c2y -std=gnu2y" />
     <Sort CPPFlags="-std=c++98 -std=gnu++98 -std=c++03 -std=gnu++03 -std=c++11 -std=gnu++11
                     -std=c++14 -std=gnu++14 -std=c++17 -std=gnu++17 -std=c++20 -std=gnu++20
-                    -std=c++23 -std=gnu++23  std=c++26 -std=gnu++26
+                    -std=c++23 -std=gnu++23  std=c++26 -std=gnu++26 -std=c++2c -std=gnu++2c
                     -static-libstdc++ -shared-libstdc++ -fpermissive -fdeduce-init-list -fcheck-new -fstrict-enums
                     -Weffc++ -Wctor-dtor-privacy -Wdelete-non-virtual-dtor -Wliteral-suffix -Wc++11-compat -Wnoexcept
                     -Wnon-virtual-dtor -Wreorder -Wstrict-null-sentinel -Wno-non-template-friend -Wnon-template-friend
Pages: 1 2 3 [4] 5 6 7 8 9 10