OSS-Fuzz ASAN Fix #844
Merged
OSS-Fuzz ASAN Fix #844
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
gittiver
approved these changes
Jun 27, 2024
|
Good afternoon! Should you get the chance, would it be possible to get this merged? I'm hoping that Google will review the OSS-Fuzz PR early this week. When this is merged in, the checks will begin passing for meeting into Google's upstream. At that point, the checks on this repo will also pass |
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.
@gittiver This PR introduces a blocking fix to
base64decodefor fuzzing integration.Currently, address sanitization instantly seg-faults when building and checking the fuzzers. This occurs when the fuzzer calls base64decode with a string of length less than 2.
When this is integrated, it will allow the Google PR to pass all CI checks and be merged in for continuous fuzzing.
Thank you for your review!