Debugging requires hard liquor.
I’ve found that 3 beers over an hour period is my sweet spot for debugging. But I would definitely need liquor to debug wine.
Way ahead of you.
Just don’t write bugs LOL
I’m more of a beer person myself.
“Is this ‘Critical Error’ the reason for the crash, or just another ill-labeled exception?”
I love WINE and it’s forks, but man, how can any program produce so many errors during optimal operation? (A rhetorical question, as I believe we all know the tragicomedic reason being Microsoft)
Tried to debug a flatpak
downloads 6GB of devel stuff, tries to open a file in gdb, cries
Finds out it is a kernel bug.
Tries to get debug logs, even though that stuff is disabled “fOr sEcUrItY hArDeNinG”
(Kernel 6.13 is a mess)
.13
Well there’s your problem.
(Not 13 specifically. Just the odd numbered sub-version in general. But 13 if you’re superstitious, I guess.)
Lol
Btw the issue was fixed upstream, Arch and Fedora have updates
Never have seen any .exe that logs anything. They’re literally black boxes.
Got to love the installer that requires a GUI
And it helpfully installs a scareware antivirus that changes your default search engine so you don’t have to go through the trouble!
