https://bugs.winehq.org/show_bug.cgi?id=51673
Olivier F. R. Dierick o.dierick@piezo-forte.be changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |o.dierick@piezo-forte.be Status|REOPENED |RESOLVED Resolution|--- |INVALID
--- Comment #20 from Olivier F. R. Dierick o.dierick@piezo-forte.be --- Hello,
(In reply to Markus Elfring from comment #16)
(In reply to Zeb Figura from comment #14) Do any developers tend to mark source code places in mentioned ways because specific functionality should actually be used? https://en.wikipedia.org/wiki/Comment_%28computer_programming%29#Tags
Yes. There are a lot of TODOs & FIXMEs and other notes in the wine source code. You may find them by searching the source code with a combination of 'find' and 'grep' commands.
(In reply to Sven Grewe from comment #17)
I'm not a developer though and the installer isn't broken. Is there any difference in how THIS one installer works on WINE and on Windows if you turn off WINE-specific logs?
No. The differences between WINE and Windows remains the same whether the logs are on or off, though, admittedly, some channels can be very verbose and cause performance degradation because the terminal doesn't scroll fast enough for such amount of text and that delays wine operation. That's why those channels are off by default.
Now back to topic;
According to the bug description and comment 13, the crash happened when starting the application and not when running the installer.
Since there is no information about the crash in this bug, I assume that the mentioned crash is the same as bug 54277 which the OP has never responded to.
Whether the crash from bug 54277 is caused by a bad install or not, it must be analyzed in that bug.
So please, if the application is still crashing with recent wine, provide feedback in the unresolved bug.
Regards.