Memory leaks and Access Violations are intrinsically bad code, with the potential for being exploited by bad-actors. In some languages, for example C++, they are easy to create. The talk demonstrates one tool, GFlags, that can be used to help to identify the presence of such bad code, and to provide confidence that once fixed, they stay fixed.