Conversation
1bsyl
changed the title
1bsyl
force-pushed
the
br_thread_error_log
branch
from
September 9, 2026 14:31
377c4ec to
12f7106
Compare
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
2 participants
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.
Maybe we could have some log information when an SDL thread terminates : so we know when it terminates, with or without error. Otherwise, the error information that is "per thread" is somehow lost and can be unoticed. (whether this is a system or user thread).
it happens I use this sometime. ( and also like to check the Error status of the main thread when it ends).
This could activated with some pre-processor "#idef", or whatever ?