I'm not aware of any such feature, and I've never heard of anybody looking for it before.
This seems like a very dangerous path to take.
What happens when you write your code to just assume that uninitialised pointers are null pointers, then you migrate your code to a new installation of your IDE, or give it to someone else? You will be propagating hard-to-find UB bugs. Not good!
Instead:
- turn on warnings for uninitialised variables
- initialise those variables
Or, for debugging existing broken code, use the fact that Visual Studio gives uninitialised data with automatic storage duration the underlying byte pattern 0xCC
. Look for this value, rather than 0x00
.