Mirrors/cppbestpractices
1
0
Fork 0
mirror of https://github.com/cpp-best-practices/cppbestpractices.git synced 2025-12-17 03:04:36 +03:00
Code Issues Actions Packages Projects Releases Wiki Activity

Add BinSkim and fuzzit to list of tools

Browse Source
This commit is contained in:
Jason Turner
2020-06-17 18:07:27 -06:00
committed by GitHub
parent c1367aa66d
commit 77810f654d
1 changed files with 10 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
02-Use_the_Tools_Available.md
View File

@@ -315,6 +315,12 @@ Both of these tools use coverage reporting to find new code execution paths and
* [LibFuzzer](http://llvm.org/docs/LibFuzzer.html)
* [KLEE](http://klee.github.io/) - Can be used to fuzz individual functions
#### Continuous Fuzzing
Continuous fuzzing tools exist to run fuzz tests for you with each commit.
* [Fuzzit](https://fuzzit.dev/)
### Mutation Testers
These tools take code executed during unit test runs and mutate the executed code. If the test continues to pass with a mutation in place, then there is likely a flawed test in your suite.
@@ -403,3 +409,7 @@ Don't forget to make sure that your error handling is being tested and works pro
### pahole
[pahole](https://linux.die.net/man/1/pahole) generates data on holes in the packing of data structures and classes in compiled code. It can also the size of structures and how they fit within the system's cache lines.
### BinSkim
[BinSkim](https://github.com/Microsoft/binskim) is a binary static analysis tool that provides security and correctness results for Windows Portable Executable and *nix ELF binary formats