SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports sorry but the page says: Note This whole page is irrelevant if you're using Windows or MacOS or Android or appimages on Linux. *** STEPS TO REPRODUCE 1. download file digiKam-7.7.0-20220325T121458-Win64.tar.xz 2. Unpack and run digikam.exe 3. Splash screen is viewing with start text "Initialize main view..." OBSERVED RESULT Splash screen disapare and nothing more happens EXPECTED RESULT Program should start If I start DigiKam 7.6 it's working and loading plugins SOFTWARE/OS VERSIONS Windows: Windows 11, 20000.556 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION The same happens with digiKam-7.7.0-20220325T121458-Win64-debug.tar.xz
The problem can be reproduced with all Windows bundles. Gilles, which GCC-10 version do we use? I had just come across the MinGW back report that setjmp is only fixed again in GCC-10.3. This backtrace looks like this: Error occurred on Saturday, March 26, 2022 at 13:34:46. digikam.exe caused an Unknown [0xC0000028] Exception at location 00007FF98CF123F6 in module ntdll.dll. AddrPC Params 00007FF98CF123F6 0000000000000002 0000000000000002 00007FF93F80D005 ntdll.dll!RtlRaiseStatus 00007FF98CE40BB3 000000EB151FBFB0 0000000000000148 000002E7EDF74A10 ntdll.dll!RtlUnwindEx 00007FF98C452EED 000000EB151FBFB0 000000000000001A 00000000FFFFF400 msvcrt.dll!_setjmpex 00007FF93F80B6FE 000000EB151FBBCC 00007FF93C44DF6A 000000EB151FBBF0 Qt5Gui.dll!QColorTrcLut::fromTransferTable 00007FF93F80BF62 000000EB151FBFB0 0000000000000000 000000EB00001800 Qt5Gui.dll!QColorTrcLut::fromTransferTable 00007FF93F80CAA8 000000EB151FBFB0 0000000100000012 000000EB00000000 Qt5Gui.dll!QColorTrcLut::fromTransferTable 00007FF93F80D005 000002E7EDF74A10 000002E7EDF74A10 0000000000000000 Qt5Gui.dll!QColorTrcLut::fromTransferTable 00007FF93F8426C1 000002E7EE11DF98 0000000000000001 000002E7F00987C0 Qt5Gui.dll!QRasterPaintEngine::fillRect 00007FF93F851098 000000EB151FF228 000002E7EE11DF58 0000000000000000 Qt5Gui.dll!QRasterPaintEngine::drawPolygon 00007FF93EA29125 000002E7F3DA9140 000002E700000005 000000EB151FF410 libdigikamgui.dll!Digikam::LabelsTreeView::goldenStarPixmap 00007FF93EA29570 000002E7EFFFD6A0 00007FF93FDE3960 000002E7EFFFCC30 libdigikamgui.dll!Digikam::LabelsTreeView::initRatingsTree 00007FF93EA2CC6E 000002E7F3DBE3F0 0000000000000002 000002E7F3DBE3F0 libdigikamgui.dll!Digikam::LabelsTreeView::initTreeView 00007FF93EA2CE48 00007FF93FDEB220 00007FF98C3F9D40 0000000000000000 libdigikamgui.dll!Digikam::LabelsTreeView::LabelsTreeView 00007FF93E980D19 0000000000000000 0000011F00000000 000002E7EE198C50 libdigikamgui.dll!Digikam::LabelsSideBarWidget::LabelsSideBarWidget 00007FF93E9645EF 00007FF93DC09290 00007FF93DB82000 000000EB151FF768 libdigikamgui.dll!Digikam::ItemIconView::ItemIconView 00007FF93E8E2175 000000EB151FF768 000000EB151FF790 000002E7EDF905C0 libdigikamgui.dll!Digikam::DigikamApp::setupView 00007FF93E8D5588 000000EB151FF8F8 000000EB151FF940 000000EB151FF920 libdigikamgui.dll!Digikam::DigikamApp::DigikamApp 00007FF626D34A99 0000000000000001 000000000000007E 00007FF626D3A078 digikam.exe!0x7ff600004a99 00007FF626D313C1 0000000000000000 0000000000000000 0000000000000000 digikam.exe!0x7ff6000013c1 00007FF626D314D6 0000000000000000 0000000000000000 0000000000000000 digikam.exe!0x7ff6000014d6 00007FF98BE67034 0000000000000000 0000000000000000 0000000000000000 KERNEL32.DLL!BaseThreadInitThunk 00007FF98CE62651 0000000000000000 0000000000000000 0000000000000000 ntdll.dll!RtlUserThreadStart Maik
It's the same crash in the bug report. We need to get back to GCC-9. https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100402 Maik
It's gcc 10.3.0 : https://github.com/mxe/mxe/blob/master/plugins/gcc10/gcc10-overlay.mk#L28 ... but when i switch from gcc 9 to 10, i forget to patch one settings to complete the transition. So there is a mix with gcc 9 and 10 while building all codes. I recompile all from scratch again... Gilles
According to the bug report, the problem is only fixed in GCC-10.4. Maik
So it's better to go back to GCC 9 ? GCC 11 is also available, but i seen bug reports about dysfunction in MXE project Gilles
Yes, at the moment GCC-9 would be the best choice if GCC-10.4 is not available. I don't think that if you rebuild everything with GCC-10.3 then it will work. Maik
Git commit a02f764269c767f646b089e7ccc423e1602b0a41 by Gilles Caulier. Committed on 27/03/2022 at 03:41. Pushed by cgilles into branch 'qt5-maintenance'. MXE: back to GCC 9 instead GCC 10. FIXED-IN: 7.7.0 M +1 -1 project/bundles/mxe/config.sh https://invent.kde.org/graphics/digikam/commit/a02f764269c767f646b089e7ccc423e1602b0a41