-
Notifications
You must be signed in to change notification settings - Fork 77
Open
Description
Is this the final version of the code? I took a rough look at the code and didn't find where some functions are implemented, such as
- WINNIE also identifies library functions that do not open or read the file themselves but instead accept a file descriptor or an in-memory buffer as input.
- WINNIE analyzes the control-flow between two API calls for paths from the return value of the invoked function to a termination condition. If such a path is found, WINNIE duplicates the decompiled control-flow code.
- Harness Validation and Finalization.
And I don't understand how the LCA results are used to guide the generation of the harness, and how to pass the seed when the APIs parameters do not contain the sample name. Maybe some complete examples would be very helpful :)
By the way, although "WINNIE's harness generator focuses testing shared libraries", many of the 59 harnesses target the executable. I am very interested in how to apply harnessgen to the main executable.
Metadata
Metadata
Assignees
Labels
No labels