From 4038e2a5642a233481ad9a7bb3419270d64a8f79 Mon Sep 17 00:00:00 2001 From: Federico Ceratto Date: Fri, 20 Jan 2017 20:48:02 +0000 Subject: [PATCH] Updated Fuzzing your nim code to rabbit out all the hard bugs (markdown) --- Fuzzing-your-nim-code-to-rabbit-out-all-the-hard-bugs.md | 5 ----- 1 file changed, 5 deletions(-) diff --git a/Fuzzing-your-nim-code-to-rabbit-out-all-the-hard-bugs.md b/Fuzzing-your-nim-code-to-rabbit-out-all-the-hard-bugs.md index fd0d3e5..5649586 100644 --- a/Fuzzing-your-nim-code-to-rabbit-out-all-the-hard-bugs.md +++ b/Fuzzing-your-nim-code-to-rabbit-out-all-the-hard-bugs.md @@ -1,8 +1,3 @@ - - - - - [afl-fuzz](http://lcamtuf.coredump.cx/afl/) is quite rabid at ferreting out issues that are hard-to-impossible to find with manual testing. While classically, afl-fuzz attempts to detect exactly the sort of issues that nim is attempting to prevent with its runtime checks in debug mode, it is by no means of no use to the nim developer. AFL is extremely good at discovering programmer errors that cannot be caught with simple user testing, even when all the safety nets are turned on.