https://bugs.winehq.org/show_bug.cgi?id=51985
Bug ID: 51985 Summary: errors significance Product: Wine Version: 6.21 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: didu31@hotmail.fr Distribution: ---
Created attachment 70972 --> https://bugs.winehq.org/attachment.cgi?id=70972 Sample of wine log.
Errors printed on stderr don't mention their significance.
They should be categorized INFO, WARNING, ERROR, FATAL as the other softwares do.
At least, FATAL errors should be mentioned as such in order to obtain a starting point for debugging.
As an example, who is able to tell what is the fatal error that causes aborting in the log here attached ?
https://bugs.winehq.org/show_bug.cgi?id=51985
--- Comment #1 from Nikolay Sivov bunglehead@gmail.com --- We have such categories already: trace, fixme, warn, err. Whether it's fatal or not depends on context. Calls to unimplemented functions or asserts will already print distinct messages.
It's not always possible to tell what went wrong from the log alone.
In your example, you're not running with vanilla wine to begin with. Is it wine-staging or some other build?
https://bugs.winehq.org/show_bug.cgi?id=51985
Zebediah Figura z.figura12@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |z.figura12@gmail.com Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID
--- Comment #2 from Zebediah Figura z.figura12@gmail.com --- It's not wine-staging, and therefore out of the scope of this bug tracker.
https://bugs.winehq.org/show_bug.cgi?id=51985
--- Comment #3 from Didier didu31@hotmail.fr --- (In reply to Nikolay Sivov from comment #1)
We have such categories already: trace, fixme, warn, err. Whether it's fatal or not depends on context. Calls to unimplemented functions or asserts will already print distinct messages.
It's not always possible to tell what went wrong from the log alone.
In your example, you're not running with vanilla wine to begin with. Is it wine-staging or some other build?
wine --version wine-6.3
https://bugs.winehq.org/show_bug.cgi?id=51985
--- Comment #4 from Didier didu31@hotmail.fr --- (In reply to Didier from comment #3)
(In reply to Nikolay Sivov from comment #1)
We have such categories already: trace, fixme, warn, err. Whether it's fatal or not depends on context. Calls to unimplemented functions or asserts will already print distinct messages.
It's not always possible to tell what went wrong from the log alone.
In your example, you're not running with vanilla wine to begin with. Is it wine-staging or some other build?
wine --version wine-6.3
(In reply to Zebediah Figura from comment #2)
It's not wine-staging, and therefore out of the scope of this bug tracker.
wine --version wine-6.3
https://bugs.winehq.org/show_bug.cgi?id=51985
--- Comment #5 from Didier didu31@hotmail.fr --- (In reply to Didier from comment #3)
It's not always possible to tell what went wrong from the log alone.
That's why I propose to add Fatal tag to the logs. As the others softwares do. A program is always able to tell what causes abort. Just ask to the exception handler, for instance.
https://bugs.winehq.org/show_bug.cgi?id=51985
--- Comment #6 from Zebediah Figura z.figura12@gmail.com --- The logs show that you have the "fsync" patch set applied to your Wine build. That's not part of upstream wine or wine-staging, regardless of what `wine --version` states.
(In reply to Didier from comment #5)
That's why I propose to add Fatal tag to the logs. As the others softwares do. A program is always able to tell what causes abort. Just ask to the exception handler, for instance.
I don't think there's anything that could be meaningfully tagged as a fatal error. Broadly speaking, we *aren't* able to tell what caused an exception, only that one happened. It's a consequence of running code that we don't control and don't know the source of.
https://bugs.winehq.org/show_bug.cgi?id=51985
--- Comment #7 from Didier didu31@hotmail.fr --- (In reply to Zebediah Figura from comment #6)
The logs show that you have the "fsync" patch set applied to your Wine build. That's not part of upstream wine or wine-staging, regardless of what `wine --version` states.
(In reply to Didier from comment #5)
That's why I propose to add Fatal tag to the logs. As the others softwares do. A program is always able to tell what causes abort. Just ask to the exception handler, for instance.
I don't think there's anything that could be meaningfully tagged as a fatal error. Broadly speaking, we *aren't* able to tell what caused an exception, only that one happened. It's a consequence of running code that we don't control and don't know the source of.
In case of windows software that decides to abort, it makes sense. Ok, I understand your point of view.
https://bugs.winehq.org/show_bug.cgi?id=51985
André H. nerv@dawncrow.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED CC| |nerv@dawncrow.de
--- Comment #8 from André H. nerv@dawncrow.de --- closing invalid
-
WineHQ Bugzilla