But I am being very specific to this use case, where a division by zero bug was found. Why couldn't you have just grepped through the codebase, found all possib

But I am being very specific to this use case, where a division by zero bug was found. Why couldn't you have just grepped through the codebase, found all possible divisions and ensured that they had a check on it to never be less than or equal to 0? The bug I located in SystemD was literally a null ptr exception. All they had to do was perform a null check on a cstring but they hadn't. I don't see the utility of reporting an LLM made fuzzer finding bugs that could be found by a lint rule or static analysis. I will appreciate a post about an LLM fuzzing software to find unique corner cases, which I predict will happen soon, in ACL controlled systems caused by policy shadowing.