You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since systemd 257, if a systemd unit fails and is restarted, and it has RestartMode=debug in its configuration, systemd will automatically set DEBUG_INVOCATION=1 for the restarted instance.
Recent GLib detects DEBUG_INVOCATION=1 and automatically turns on debug logging. Steam's pressure-vessel does similarly, even if it happens to have been compiled/linked against older GLib (in practice it usually is).
I realise that it's relatively unlikely for a systemd service to be written using SDL, but perhaps it would be helpful for SDL to do this too, to spread the meme that DEBUG_INVOCATION=1 is a good general-purpose way to say "more information, please"?
I think the ideal handling would be to turn on some reasonable level of debug logging (for example the equivalent of SDL12COMPAT_DEBUG_LOGGING=1 and SDL2COMPAT_DEBUG_LOGGING=1 would probably be appropriate), but try not to increase the log level so much that important information is lost in the noise (so for example logging individual input events would probably be too much).
I don't know what that should mean in SDL-world: perhaps raising the default for everything to DEBUG level? The calls to SDL_LogDebug() within SDL itself don't look too noisy to me, and mostly they seem to be things that would typically happen either once per run (like detecting whether to use udev or inotify for Linux input device enumeration), or only when something "big" happens (like creating a window with Vulkan rendering enabled, or plugging/unplugging a game controller), or only when something unexpected or non-ideal happens (like inability to parse various HID reports).
The text was updated successfully, but these errors were encountered:
This seems reasonable, SDL_HINT_LOGGING is currently documented like this:
* If this hint isn't set, the default log levels are equivalent to:
*
* `app=info,assert=warn,test=verbose,*=error`
That could change to:
* If this hint isn't set, the default log levels are equivalent to:
*
* `app=info,assert=warn,test=verbose,*=error`
*
* If the `DEBUG_INVOCATION` environment variable is set to "1", the default log levels are equivalent to:
*
* `assert=warn,test=verbose,*=debug`
Since systemd 257, if a systemd unit fails and is restarted, and it has
RestartMode=debug
in its configuration, systemd will automatically setDEBUG_INVOCATION=1
for the restarted instance.Recent GLib detects
DEBUG_INVOCATION=1
and automatically turns on debug logging. Steam's pressure-vessel does similarly, even if it happens to have been compiled/linked against older GLib (in practice it usually is).I realise that it's relatively unlikely for a systemd service to be written using SDL, but perhaps it would be helpful for SDL to do this too, to spread the meme that
DEBUG_INVOCATION=1
is a good general-purpose way to say "more information, please"?I think the ideal handling would be to turn on some reasonable level of debug logging (for example the equivalent of
SDL12COMPAT_DEBUG_LOGGING=1
andSDL2COMPAT_DEBUG_LOGGING=1
would probably be appropriate), but try not to increase the log level so much that important information is lost in the noise (so for example logging individual input events would probably be too much).I don't know what that should mean in SDL-world: perhaps raising the default for everything to DEBUG level? The calls to
SDL_LogDebug()
within SDL itself don't look too noisy to me, and mostly they seem to be things that would typically happen either once per run (like detecting whether to use udev or inotify for Linux input device enumeration), or only when something "big" happens (like creating a window with Vulkan rendering enabled, or plugging/unplugging a game controller), or only when something unexpected or non-ideal happens (like inability to parse various HID reports).The text was updated successfully, but these errors were encountered: