according to MSDN, Visual Studio uses a special heap in debug mode that has extra "no man s land" bytes set to 0xFD by default to track heap corruption Is there a way to force visual to break when such values are overwritten? I can t find this information anywhere and it seems extremely useful, much more than having to manually dump the memstat like MSDN proposes
感谢