Repository navigation
Logging: improve suppression thread safety; fix file/line logging in gamelogic - #1829
Merged
Merged
Conversation
In the engine, access the logs.suppression.* cvars through their objects, instead of looking them up in the cvar map via their names. Looking them up via name is seriously unsafe on a non-main thread. Simply reading the int or bool is still technically thread-unsafe, but should be fine in practice. The gamelogic still has to look up cvars by name, but there is no issue because logging is prohibited on non-main threads. Fixes, for practical purposes, DaemonEngine/Daemon-vulkan#21.
logs.writeSrcLocation.* cvars no longer emit warnings due to duplicate registration, and are obeyed by the gamelogic.
slipher
force-pushed
the
logging-fixes
branch
from
September 29, 2025 01:03
bb03d5e to
a235cb3
Compare
VReaperV
approved these changes
Oct 5, 2025
Member
|
@slipher I now get this linkage error: |
Member
|
Ah no it's a false alarm. That's one of the very rare case where CMake fails to properly invalidate the targets and fails at rebuilding the executable. Deleting the build folder fixed it. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
In the engine, access the
logs.suppression.*cvars through their objects, instead of looking them up in the cvar map via their names. Looking them up via name is seriously unsafe on a non-main thread. Simply reading the int or bool is still technically thread-unsafe, but should be fine in practice.Fix
logs.writeSrcLocation.*access in gamelogic. These cvars will no longer emit warnings due to duplicate registration, and be obeyed by the gamelogic.