https://bugs.winehq.org/show_bug.cgi?id=47356
Bug ID: 47356 Summary: By default only echo errors and traces Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: es20490446e@gmail.com Distribution: ---
As said in: https://wiki.winehq.org/Debug_Channels
By default Wine echoes all debug channels. For the end user it would be more meaningful only to echo "err" and "trace" by default.
Plus echoing the rest of channels even noticeably slowed down my computer on certain scenarios. It even froze it when saving the echo into a variable, or redirecting to a file.
Programs should only print messages that would require an action by the kind of user in front of the screen.
https://bugs.winehq.org/show_bug.cgi?id=47356
Zebediah Figura z.figura12@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |z.figura12@gmail.com
--- Comment #1 from Zebediah Figura z.figura12@gmail.com --- (In reply to Alberto Salvia Novella from comment #0)
As said in: https://wiki.winehq.org/Debug_Channels
By default Wine echoes all debug channels. For the end user it would be more meaningful only to echo "err" and "trace" by default.
Plus echoing the rest of channels even noticeably slowed down my computer on certain scenarios. It even froze it when saving the echo into a variable, or redirecting to a file.
Programs should only print messages that would require an action by the kind of user in front of the screen.
That's really not how it works, I think you're confusing our "channels" and "classes". "Channels" describe component, "classes" describe severity. We only report the most severe messages (FIXME, ERR) and ignore the least (WARN, TRACE) by default. That should never result in slowdown from logging. If it does, it probably means a specific message needs to be silenced.
Having ERR, FIXME on by default is entirely a debugging tool. It's good for a spot check if programs fail, because it will diagnose a problem generally with little to no overhead. Normally a user is expected to not run an application from the terminal, or to run with WINEDEBUG=-all. (I have my qualms with this policy, but.)
https://bugs.winehq.org/show_bug.cgi?id=47356
--- Comment #2 from Alberto Salvia Novella es20490446e@gmail.com --- We could make the documentation to clarify that, because I thought that TRACE was the highest priority.
FIXME usually is the one causing trouble, as it spams the same message over and over again in some games. For example if certain texture has a failure, it will spam the message for every loaded texture.
Most likely only ERR is relevant to the average user, so to let them know why the software stopped working.
WINEDEBUG=warn-all,fixme-all,trace-all
https://bugs.winehq.org/show_bug.cgi?id=47356
Alberto Salvia Novella es20490446e@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Summary|By default only echo errors |By default only echo errors |and traces |
https://bugs.winehq.org/show_bug.cgi?id=47356
--- Comment #3 from Zebediah Figura z.figura12@gmail.com --- (In reply to Alberto Salvia Novella from comment #2)
We could make the documentation to clarify that, because I thought that TRACE was the highest priority.
FIXME usually is the one causing trouble, as it spams the same message over and over again in some games. For example if certain texture has a failure, it will spam the message for every loaded texture.
Most likely only ERR is relevant to the average user, so to let them know why the software stopped working.
WINEDEBUG=warn-all,fixme-all,trace-all
The only thing that the average user should really care to see is anything in the "winediag" channel, which is always ERR. So really the recommended usage should be WINEDEBUG=-all,+winediag or -all,err+winediag. I'll edit the page to try to make this and some other things clearer.
https://bugs.winehq.org/show_bug.cgi?id=47356
Fabian Maurer dark.shadow4@web.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |dark.shadow4@web.de
--- Comment #4 from Fabian Maurer dark.shadow4@web.de ---
The only thing that the average user should really care to see is anything in the "winediag" channel, which is always ERR.
Well, that and some messages that don't follow debug channels (WINE_MESSAGE). Unless those errors should also be in the "winediag" channel instead.
https://bugs.winehq.org/show_bug.cgi?id=47356
--- Comment #5 from Zebediah Figura z.figura12@gmail.com --- (In reply to Fabian Maurer from comment #4)
The only thing that the average user should really care to see is anything in the "winediag" channel, which is always ERR.
Well, that and some messages that don't follow debug channels (WINE_MESSAGE). Unless those errors should also be in the "winediag" channel instead.
Sure, but those have no channel. I also am not particularly sure why that macro exists.
https://bugs.winehq.org/show_bug.cgi?id=47356
--- Comment #6 from Alberto Salvia Novella es20490446e@gmail.com --- To me it looks like there are only two different scenarios. Messages that matter to the end user, and messages that matter to a developer.
The rest of granularity just makes deciding on it harder.
https://bugs.winehq.org/show_bug.cgi?id=47356
--- Comment #7 from Zebediah Figura z.figura12@gmail.com --- I've tried to better document debug classes in the aforementioned wiki page. I've also removed or rewritten a lot of information that was out of date. Please let me know if you feel like it could use more clarification in any place.
https://bugs.winehq.org/show_bug.cgi?id=47356
--- Comment #8 from Alberto Salvia Novella es20490446e@gmail.com --- https://youtu.be/_xS13nBgmO8
https://bugs.winehq.org/show_bug.cgi?id=47356
--- Comment #9 from Alberto Salvia Novella es20490446e@gmail.com --- Thanks, the new documentation seems quite clear to me.
Is err less severe than fixme?
Cause I frequently see fixme messages, but programs seem to continue working properly.
https://bugs.winehq.org/show_bug.cgi?id=47356
--- Comment #10 from Zebediah Figura z.figura12@gmail.com --- (In reply to Alberto Salvia Novella from comment #9)
Thanks, the new documentation seems quite clear to me.
Is err less severe than fixme?
Cause I frequently see fixme messages, but programs seem to continue working properly.
Eh.
It's probably more likely that a FIXME is harmless than that an ERR is harmless. But FIXME is also used to mean, in a way, "this is completely broken and won't work at all".
https://bugs.winehq.org/show_bug.cgi?id=47356
--- Comment #11 from Alberto Salvia Novella es20490446e@gmail.com --- I see.
https://bugs.winehq.org/show_bug.cgi?id=47356
Alberto Salvia Novella es20490446e@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED
--- Comment #12 from Alberto Salvia Novella es20490446e@gmail.com --- Fixing in the documentation seems enough.
https://bugs.winehq.org/show_bug.cgi?id=47356
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #13 from Alexandre Julliard julliard@winehq.org --- Closing bugs fixed in 4.13.
-
wine-bugs＠winehq.org