We are (slowly...) doing the same thing across our codebase. The tool we use -- PVS-Studio -- just introduced checking for uninit&#x27;d scalars so we are grinding those down and doing eyeball checks in the ctors, but I was hoping for a more reliable method for the latter portion.<p>Thanks for &#x2F;SDL! This looks like it may be very promising: <a href="http:&#x2F;&#x2F;blogs.microsoft.com&#x2F;cybertrust&#x2F;2012&#x2F;06&#x2F;06&#x2F;warnings-sdl-and-improving-uninitialized-variable-detection&#x2F;" rel="nofollow">http:&#x2F;&#x2F;blogs.microsoft.com&#x2F;cybertrust&#x2F;2012&#x2F;06&#x2F;06&#x2F;warnings-sd...</a><p>At the very least that would help remove random behavior at the cost of speed (if I understand correctly). I&#x27;ll have to sleep on &#x2F;SDL and do some perf testing come Monday. I had really wanted to use &#x2F;analyze (<a href="https:&#x2F;&#x2F;msdn.microsoft.com&#x2F;en-us&#x2F;library&#x2F;d3bbz7tz%28v=VS.100%29.aspx" rel="nofollow">https:&#x2F;&#x2F;msdn.microsoft.com&#x2F;en-us&#x2F;library&#x2F;d3bbz7tz%28v=VS.100...</a>) but it crashes! D:<p>Unfortunately, I&#x27;m rooted in Windows SDK and I don&#x27;t think clang supports that. The Microsoft Application Verifier has some run-time memory checks, so I&#x27;m not totally unarmed.<p>I looked at PC-lint doesn&#x27;t have complete support for C++11 yet and I&#x27;m worried about the rate of false positives. I had not heard of cppcheck, so I&#x27;ll have to give that go since it looks free.<p>Thanks for the info!