What you need is a debugger, not fwrite or printf.
Visual Studio has a nice debugger, and within its sortiment, it allows you to put breakpoints when a certain position in memory changes (in other words, you can have it break when your buffer is changed, or corrupted), to see what caused the change.
It makes debugging so much easier.
Originally Posted by Adak
Generally, no as the behavior is undefined; anything can happen. You're lucky if id does crash.
However, it is possible to make it always crash with a good debugger which overwrites freed memory with very high or very low constants, such that dereferencing them would result in a segfault. Similarly global delete can be overridden to do the same thing.
MS Visual Studio seems to have such a debugger.
It is too clear and so it is hard to see.
A dunce once searched for fire with a lighted lantern.
Had he known what fire was,
He could have cooked his rice much sooner.
