Infer# performs cross-assembly analysis to find issues like null pointer dereferences, resource leaks, and thread safety violations, in addition to security vulnerabilities like SQL injections and DLL injections. It uses incorrectness separation logic, one of the latest advancements in program analysis research, to mathematically prove the presence of bugs in code. Infer# takes a different approach from other tools you’ve heard of – it derives summaries of each method’s semantics and reasons over the program’s behavior. Microsoft open-sourced Infer# in 2020, which leverages Meta’s Infer. In today’s post, we’re going to show you how Infer# can help you put down these zombie bugs, once and for all. Unfortunately, due to the huge variation and complexity of coding constructs and conventions in different projects, this approach often leads to the high false positive and false negative rates for which static analysis tools are notorious. There are many static analysis tools on the marketplace today to help you detect bugs, many of which work by searching for a series of syntactic patterns in code. We’ve all suffered from “zombie bugs” before. Your night of the living dead has begun – no matter how many times you try to put this bug down, it just keeps coming back to life.
Finally, you find it, push the fix, and reboot the application. Morning soon passes to afternoon, fading into dusk. Heaving a heavy sigh, you soon find yourself sifting through tens of thousands of lines of code and logs. Another high severity ticket – your servers have crashed, and you have by tomorrow morning to figure out why. You slide into your office chair, cup of coffee in hand, and check your email.
0 kommentar(er)
