feat: add fuzzing harnesses #925
Open
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
|
This should work now and hopefully pass all tests, once this gets merged I can open a PR (which is ready locally) on the OSS-Fuzz side of things |
This was referenced Feb 5, 2025
|
@facontidavide, I thought I had the pre-commit fixed, looks like I forgot to push the changes to the corpus files. Please re-run the workflow, it should be all good now :). Also, if you're about to merge this, drop a comment in google/oss-fuzz#13008 to drive this effort forward, thanks! |
|
@facontidavide kind reminder to get this merged, Google approved of the integration and its just a matter of getting this PR in now and you dropping an |
|
yes, this is on my radar |
# for free
to join this conversation on GitHub.
Already have an account?
# 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.
I still have a bunch of other crashes, esp. for the type-system and casting. I figured why not try to up-stream the fuzzing efforts to have it saved in a central place.
While we're at it, I'd like to add this project to OSS-Fuzz and would prepare an appropriate PR for this next. If it gets approved, it would mean continuous fuzzing/testing for BehaviorTree.CPP and bug reports would come your way without e.g. me having to file anything.
That said, to get that one merged over there, I will need your approval from one of the maintainers here. Eying @facontidavide or @miccol. What do you think? Would that be something you guys would be interested in?