Buffer overruns

[kelvin.koogan]

Anyone any good ways of debugging buffer overruns? The buffer overrun
seems to be detected during garbage collection, judging by the call
stack, so I have no idea where the actual overrun took place. Is there
anyway I can get a handle on the buffer which is experiencing the
problem?

Googling the problem suggests using windbg, but I'm not having any joy
with that.

TIA,
KK

 

[Ben Voigt [C++ MVP]]

You need something like electric fence.
http://directory.fsf.org/project/ElectricFence/

I have no idea where you might find a .NET equivalent.

You could always compile with /clr:safe, that will point out where you are
using pointer arithmetic (and thus possibly overrunning).