Sadly Visual Studio&#x27;s compiler has no warning I&#x27;m aware of.  Using &#x2F;sdl will forcibly initialize all your members however - I guess Microsoft&#x27;s approach to the problem is that fixing it for you is better than giving you ignore-able warnings.<p>There are third party tools - such as cppcheck - which should catch uninitialized members however.<p>I generally also compile with clang, which catches a lot of additional stuff for me.<p>And here&#x27;s a random John Carmack link noting some of the static analysis tools out there:<p><a href="http:&#x2F;&#x2F;www.gamasutra.com&#x2F;view&#x2F;news&#x2F;128836&#x2F;InDepth_Static_Code_Analysis.php" rel="nofollow">http:&#x2F;&#x2F;www.gamasutra.com&#x2F;view&#x2F;news&#x2F;128836&#x2F;InDepth_Static_Cod...</a><p>I&#x27;ve been playing around with clang&#x27;s Address Sanitizer all day as well, catching buffer overflows and underflows left and right in a janky old codebase I was suddenly thrust into recently...