I faced temporarily a similar issue while building a single file. However by investigating the error-Output of Code::Blocks I came to the same conclusion as you:
* The initial root cause is crash of the compiler.
* MinGW 13.2.0 UCRT 64 published by MSYS2.
* running on Windows 10.
[100.0%] x86_64-w64-mingw32-g++.exe -Wnon-virtual-dtor -Wshadow -Winit-self -Wredundant-decls -Wcast-align -Wundef -Wfloat-equal -Winline -Wunreachable-code -Wmissing-declarations -Wmissing-include-dirs -Wswitch-enum -Wswitch-default -Weffc++ -Wzero-as-null-pointer-constant -Wmain -pedantic-errors -pedantic -Wextra -Wall -std=c++14 -pipe -mthreads -isystem C:\Lib\wxWidgets\3_2_4\include -isystem ......\sources\tinyxml -D__GNUWIN32__ -D__WXMSW__ -DWXUSINGDLL -fomit-frame-pointer -fexpensive-optimizations -O3 -IC:\Lib\wxWidgets\3_2_4\include -I......\sources\KanjiNoKenkyuu -I......\sources\tinyxml -I......\sources\analysis -I......\sources\dataBase -I......\sources\view -I......\sources\view\symbol -I......\sources\view\tree -I......\sources\view\logging -I......\sources\view\dialogue -I......\sources\view\pictograph -I......\sources\view\pictograph\draw -I......\sources\view\description -I......\sources\dataBase\command -I......\sources\dataBase\symbol -I......\sources\dataBase\symbol\command -I......\sources\dataBase\description -I......\sources\dataBase\description\command -I......\sources\dataBase\pictograph -I......\sources\dataBase\pictograph\command -I......\sources\dataBase\association -I......\sources\dataBase\association\command -I......\sources\dataBase\template -I......\sources\dataBase\template\command -I......\sources\dataBase\label -I......\sources\dataBase\label\command -I......\sources\dataBase\font -I......\sources\dataBase\font\command -c C:\Project\Nihongo_Shiryou\SandBox\trunk\sources\view\dialogue\fnt_Dlg_FontCharacter.cpp -o obj\Release\sources\view\dialogue\fnt_Dlg_FontCharacter.o
In file included from C:/Tool/Development/MinGW/MinGW_13_2_0_MSYS/ucrt64/lib/gcc/x86_64-w64-mingw32/13.2.0/include/immintrin.h:104,
from C:/Tool/Development/MinGW/MinGW_13_2_0_MSYS/ucrt64/lib/gcc/x86_64-w64-mingw32/13.2.0/include/x86intrin.h:32,
from C:/Tool/Development/MinGW/MinGW_13_2_0_MSYS/ucrt64/include/winnt.h:1658,
from C:/Tool/Development/MinGW/MinGW_13_2_0_MSYS/ucrt64/include/minwindef.h:163,
from C:/Tool/Development/MinGW/MinGW_13_2_0_MSYS/ucrt64/include/windef.h:9,
from C:/Tool/Development/MinGW/MinGW_13_2_0_MSYS/ucrt64/include/windows.h:69,
from C:/Tool/Development/MinGW/MinGW_13_2_0_MSYS/ucrt64/include/winsock2.h:23,
from C:\Lib\wxWidgets\3_2_4\include/wx/msw/wrapwin.h:46,
from C:\Lib\wxWidgets\3_2_4\include/wx/atomic.h:45,
from C:\Lib\wxWidgets\3_2_4\include/wx/sharedptr.h:14,
from C:\Lib\wxWidgets\3_2_4\include/wx/dialog.h:16,
from C:\Lib\wxWidgets\3_2_4\include/wx/msgdlg.h:18,
from C:\Project\Nihongo_Shiryou\SandBox\trunk\sources\view\dialogue\user_out.h:20,
from C:\Project\Nihongo_Shiryou\SandBox\trunk\sources\view\dialogue\fnt_Dlg_FontCharacter.cpp:22: C:/Tool/Development/MinGW/MinGW_13_2_0_MSYS/ucrt64/lib/gcc/x86_64-w64-mingw32/13.2.0/include/avx512fp16vlintrin.h:753:1: internal compiler error: Segmentation fault
753 | }
| ^
libbacktrace could not find executable to open
Please submit a full bug report, with preprocessed source (by using -freport-bug).
See https://github.com/msys2/MINGW-packages/issues for instructions.
Process terminated with status 1 (0 minute(s), 25 second(s))
1 error(s), 0 warning(s) (0 minute(s), 25 second(s))
You see in the lower part compiler-output mentioning a internal compiler error: Segmentation fault.
This happens not with every build. Even you start the build again for a file where the build crashed before it succeeds with the next build.
What is irritating is the fact that the first part of the error-output is mentioning an error in the included headers what is misleading you if you don't recognize that this is actually an issue of the compiler itself.
Even I agree that this is actually not caused by Code::Blocks I wonder what has changed while the nightly 13456 (06.03.2024) and the nightly 13493 (24.06.2024) since I frequently used this build-suite 27.02.2024 for single file builds as well as for project builds and until the 13493 (24.06.2024) I never faced this issue and I have not modified my build configuration.
I wish you all happy Eastern,
Eckard Klotz.
Last edit: Eckard Klotz 2024-03-30
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Use the forum for this kind of problem. You must give way more information, see the FAQ in the Wiki
Hello Miguel Gimenez.
It seems that this issue is the same as described in the Error Report by Nenin .
I faced temporarily a similar issue while building a single file. However by investigating the error-Output of Code::Blocks I came to the same conclusion as you:
* The initial root cause is crash of the compiler.
* MinGW 13.2.0 UCRT 64 published by MSYS2.
* running on Windows 10.
You see in the lower part compiler-output mentioning a internal compiler error: Segmentation fault.
This happens not with every build. Even you start the build again for a file where the build crashed before it succeeds with the next build.
What is irritating is the fact that the first part of the error-output is mentioning an error in the included headers what is misleading you if you don't recognize that this is actually an issue of the compiler itself.
Even I agree that this is actually not caused by Code::Blocks I wonder what has changed while the nightly 13456 (06.03.2024) and the nightly 13493 (24.06.2024) since I frequently used this build-suite 27.02.2024 for single file builds as well as for project builds and until the 13493 (24.06.2024) I never faced this issue and I have not modified my build configuration.
I wish you all happy Eastern,
Eckard Klotz.
Last edit: Eckard Klotz 2024-03-30