-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix unhandled null characters in Android logs #12743
Merged
james7132
merged 7 commits into
bevyengine:main
from
james7132:fix-android-log-unsoundness
Mar 29, 2024
Merged
Fix unhandled null characters in Android logs #12743
james7132
merged 7 commits into
bevyengine:main
from
james7132:fix-android-log-unsoundness
Mar 29, 2024
Conversation
This file contains 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
james7132
added
O-Android
Specific to the Android mobile operating system
A-Diagnostics
Logging, crash handling, error reporting and performance analysis
P-Unsound
A bug that results in undefined compiler behavior
labels
Mar 27, 2024
Kanabenki
reviewed
Mar 27, 2024
BD103
suggested changes
Mar 27, 2024
BD103
approved these changes
Mar 28, 2024
Kanabenki
approved these changes
Mar 28, 2024
github-merge-queue
bot
removed this pull request from the merge queue due to failed status checks
Mar 28, 2024
matiqo15
approved these changes
Mar 28, 2024
matiqo15
added
the
S-Ready-For-Final-Review
This PR has been approved by the community. It's ready for a maintainer to consider merging it
label
Mar 28, 2024
github-merge-queue
bot
removed this pull request from the merge queue due to failed status checks
Mar 29, 2024
github-merge-queue
bot
removed this pull request from the merge queue due to failed status checks
Mar 29, 2024
mockersf
pushed a commit
that referenced
this pull request
Apr 1, 2024
# Objective Fix #12728. Fix unsoundnesss from unhandled null characters in Android logs. ## Solution Use `CString` instead of using formatted Strings. Properly document the safety invariants of the FFI call.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
A-Diagnostics
Logging, crash handling, error reporting and performance analysis
O-Android
Specific to the Android mobile operating system
P-Unsound
A bug that results in undefined compiler behavior
S-Ready-For-Final-Review
This PR has been approved by the community. It's ready for a maintainer to consider merging it
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.
Objective
Fix #12728. Fix unsoundnesss from unhandled null characters in Android logs.
Solution
Use
CString
instead of using formatted Strings. Properly document the safety invariants of the FFI call.