Skip to content

Commit

Permalink
Merge pull request #164 from JannisBush/patch-1
Browse files Browse the repository at this point in the history
Fix incorrect link (ConstraintFuzzer got renamed to FuzzingWithConstraints)
  • Loading branch information
andreas-zeller committed Jan 18, 2024
2 parents da88275 + 65d217a commit 297d445
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion notebooks/Grammars.ipynb
Expand Up @@ -1629,7 +1629,7 @@
}
},
"source": [
"One way around this is to attach constraints to grammars, as we will discuss [later in this book](ConstraintFuzzer.ipynb). Another possibility is to put together the strengths of grammar-based fuzzing and [mutation-based fuzzing](MutationFuzzer.ipynb). The idea is to use the grammar-generated inputs as *seeds* for further mutation-based fuzzing. This way, we can explore not only _valid_ inputs, but also check out the _boundaries_ between valid and invalid inputs. This is particularly interesting as slightly invalid inputs allow finding parser errors (which are often abundant). As with fuzzing in general, it is the unexpected which reveals errors in programs."
"One way around this is to attach constraints to grammars, as we will discuss [later in this book](FuzzingWithConstraints.ipynb). Another possibility is to put together the strengths of grammar-based fuzzing and [mutation-based fuzzing](MutationFuzzer.ipynb). The idea is to use the grammar-generated inputs as *seeds* for further mutation-based fuzzing. This way, we can explore not only _valid_ inputs, but also check out the _boundaries_ between valid and invalid inputs. This is particularly interesting as slightly invalid inputs allow finding parser errors (which are often abundant). As with fuzzing in general, it is the unexpected which reveals errors in programs."
]
},
{
Expand Down

0 comments on commit 297d445

Please sign in to comment.