8000 Add option to output execution traces during fuzzing by novafacing · Pull Request #81 · intel/tsffs · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Add option to output execution traces during fuzzing #81

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

Jump to bottom
Merged
merged 5 commits into from
Apr 25, 2024
Merged

Add option to output execution traces during fuzzing #81

merged 5 commits into from
Apr 25, 2024

Conversation

novafacing
Copy link
Contributor

This adds options:

tsffs.save_interesting_execution_traces: bool
tsffs.save_all_execution_traces: bool
tsffs.save_solution_execution_traces: bool
tsffs.execution_trace_directory: Path

Which enables saving execution traces for various types of executions to be reviewed at a later time. Care should be taken when enabling these options, and it should typically be used for debug/testing, because enabling any execution trace saving enables recording of traces for all executions (because we do not know which are interesting until the end, and so forth). Thus enabling any trace saving has a very large performance penalty.

@novafacing novafacing mentioned this pull request Apr 21, 2024
Open
8000
@novafacing novafacing merged commit 592a8df into intel:main Apr 25, 2024
16 checks passed
@novafacing novafacing deleted the execution-traces branch April 25, 2024 20:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@tklengyel 5609 tklengyel tklengyel approved these changes

@brandonmarken brandonmarken Awaiting requested review from brandonmarken

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@novafacing @tklengyel
0