Skip to content

Fix heterogen-fuzz throwing segfault due to missing good-outputs folder #2

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.

Sign up for GitHub

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

Open
chenhongqiao wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Fix heterogen-fuzz throwing segfault due to missing good-outputs folder #2

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
efb26a0
fix fuzzing signal 11
chenhongqiao Jun 21, 2023
a7d731d
document heterogen-fuzz output_dir
chenhongqiao Jun 21, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Empty file added 2-test-generation/good-outputs/.gitkeep
View file
Open in desktop
Empty file.
2 changes: 2 additions & 0 deletions 2-test-generation/readme.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -30,4 +30,6 @@ Go back to the `2-test-generation` folder, type the following command:
```bash
./heterogen-fuzz good-seeds/ good-outputs/ 1000 ../test-program/a.out
```
Make sure output folder exists before using heterogen-fuzz.

You can find the generated test inputs in `good-outputs` folder. The generated inputs will be used to check behavior preservation in the automated code edit process. This step generates the results presented in Table 4. Please note that fuzzing is a random test generation process; thus, the results vary significantly across different runs.