forked from zeux/meshoptimizer
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
gltfpack: Implement end-to-end fuzzing build mode
While individual components of gltfpack like cgltf or mesh encoders have their own dedicated fuzzers, gltfpack has a lot of code that can be difficult to validate. We would expect that gltfpack is resistant to invalid inputs (with the exception, perhaps, of .obj inputs where fast_obj, the library we use, is currently not fuzz safe). This change implements a in-memory GLB loading flow (parseGlb) and an in-memory fuzzer; we disable all file I/O by using NULL paths, and otherwise share all the same processing code with the exception of final buffer writing.
- Loading branch information
Showing
5 changed files
with
71 additions
and
14 deletions.
There are no files selected for viewing
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 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 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 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 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