| Summary: | digiKam-8.1.0-20230517T153157-Win64-debug will not Open after Installation | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | Galen Adams <gadams3rd> |
| Component: | Bundle-Windows | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | caulier.gilles, metzpinguin |
| Priority: | NOR | ||
| Version First Reported In: | 8.1.0 | ||
| Target Milestone: | --- | ||
| Platform: | Microsoft Windows | ||
| OS: | Microsoft Windows | ||
| Latest Commit: | Version Fixed/Implemented In: | 8.1.0 | |
| Sentry Crash Report: | |||
| Attachments: |
attachment-2601184-0.html
attachment-2661954-0.html digiKam-8.1.0-20230522T042418-Win64-debug.png attachment-3141514-0.html attachment-3166801-0.html attachment-3225413-0.html |
||
|
Description
Galen Adams
2023-05-18 17:31:39 UTC
Windows 10 or 11? With Windows 10 there are no problems with the current digiKam-8.1.0 version from 05/17/2023. So a DebugView log would be of interest. Maik For the debugview usage, see the contribute web page : https://www.digikam.org/contribute/ Gilles Caulier Created attachment 159085 [details] attachment-2601184-0.html Windows 7 Pro Can I Debug View even when it will not Open ? On Thu, May 18, 2023 at 3:33 PM <bugzilla_noreply@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=469960 > > --- Comment #2 from caulier.gilles@gmail.com --- > For the debugview usage, see the contribute web page : > > https://www.digikam.org/contribute/ > > Gilles Caulier > > -- > You are receiving this mail because: > You reported the bug. yes sure. It's a generic log/events viewer Created attachment 159109 [details] attachment-2661954-0.html I am sorry, but this DeBug View business must be way over my head; the more I search for information, the more confused I become; and, I have been down a hundred useless rabbit holes. The 20230517 win64 Non-DeBug version starts and seems to work fine. Immediately upon clicking the TaskBar icon, the Debug version gives a notice that it cannot open. On Thu, May 18, 2023 at 3:59 PM <bugzilla_noreply@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=469960 > > --- Comment #4 from caulier.gilles@gmail.com --- > yes sure. It's a generic log/events viewer > > -- > You are receiving this mail because: > You reported the bug. Created attachment 159235 [details] digiKam-8.1.0-20230522T042418-Win64-debug.png I tried the 0522 debug version and it behaves no better than the 0517 version. The non-debug mates to these open and run. It puzzles me that the non-debug versions will work and the debug versions will not. [image: digiKam-8.1.0-20230522T042418-Win64-debug.png] On Fri, May 19, 2023 at 9:50 AM Galen Adams <gadams3rd@gmail.com> wrote: > I am sorry, but this DeBug View business must be way over my head; the > more I search for information, the more confused I become; and, I have been > down a hundred useless rabbit holes. > > The 20230517 win64 Non-DeBug version starts and seems to work fine. > > Immediately upon clicking the TaskBar icon, the Debug version gives a > notice that it cannot open. > > On Thu, May 18, 2023 at 3:59 PM <bugzilla_noreply@kde.org> wrote: > >> https://bugs.kde.org/show_bug.cgi?id=469960 >> >> --- Comment #4 from caulier.gilles@gmail.com --- >> yes sure. It's a generic log/events viewer >> >> -- >> You are receiving this mail because: >> You reported the bug. > > Why are you even using the debug version? @Gilles, the debug version has the same file size as the normal one, I think there is something wrong here. Maik Created attachment 159238 [details] attachment-3141514-0.html " Why are you even using the debug version?" In case I was asked to run a bug trace The debug versions have always worked before. On Thu, May 25, 2023 at 3:14 AM Maik Qualmann <bugzilla_noreply@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=469960 > > --- Comment #7 from Maik Qualmann <metzpinguin@gmail.com> --- > Why are you even using the debug version? > @Gilles, the debug version has the same file size as the normal one, I > think > there is something wrong here. > > Maik > > -- > You are receiving this mail because: > You reported the bug. The Debug version is not required to create the DebugView output. Maik It's must be not exactly the same size. The debug must be a little bit larger. But i agree, in fact if all debug symbols are present in all internal libs, plugins and executable from digiKam (not the dependencies), the size of the bundle will be largest than 2Gb, and NSIS is not able to package more than 2GB (it crash, it's limitation of Windows API used internally, eg the win32 stuff of course)... So, i created the bundle with just the minimum of debug symbols, using the mingw-strip tool to drop the object. The error report by windows at run time is probably due to a chunk of symbols to much dropped from the binaries. I will double check this point this evening. Gilles Created attachment 159255 [details] attachment-3166801-0.html "The Debug version is not required to create the DebugView output." My understanding of the debug version was that digiKam could create/do it's own bug tracking "in-house". If that is not the case, then what is the debug version for ? Thanks for your patience with my poor understanding of such things. On Thu, May 25, 2023 at 8:36 AM <bugzilla_noreply@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=469960 > > --- Comment #10 from caulier.gilles@gmail.com --- > It's must be not exactly the same size. The debug must be a little bit > larger. > > But i agree, in fact if all debug symbols are present in all internal libs, > plugins and executable from digiKam (not the dependencies), the size of the > bundle will be largest than 2Gb, and NSIS is not able to package more than > 2GB > (it crash, it's limitation of Windows API used internally, eg the win32 > stuff > of course)... > > So, i created the bundle with just the minimum of debug symbols, using the > mingw-strip tool to drop the object. The error report by windows at run > time is > probably due to a chunk of symbols to much dropped from the binaries. I > will > double check this point this evening. > > Gilles > > -- > You are receiving this mail because: > You reported the bug. The debug installer included more binary symbols fro a debugger. If application crash, we can get a back-trace of internal calls in the program with the places where code is called. The non debug installer do not includes these extra symbols. If application crash the back-trace will be limited to the binary code without information about the code called. DebugView program has nothing to do with the debugger back-trace. It just capture the trace printed in the console when application run. Under Linux, when you run digiKam in the console you see directly these traces. Under Windows this concept do not exists, you need an extra application to do the job... The crash with debug binary under windows is now fixed. Stripping executable was the problem... Created attachment 159262 [details] attachment-3225413-0.html Thank You so very much ! Much appreciated. On Thu, May 25, 2023 at 1:12 PM <bugzilla_noreply@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=469960 > > --- Comment #13 from caulier.gilles@gmail.com --- > The crash with debug binary under windows is now fixed. Stripping > executable > was the problem... > > -- > You are receiving this mail because: > You reported the bug. |