detect stack corruption

Question

Sometimes some code portion in my application corrupts the stack. But the problem will be visible only after some time. So we cannot identify the exact location of the problem. Is there any tools available to detect stack corruption in a c++ application immediately after corrupting the stack?

Is there any windbg tools to identify this?

See http://stackoverflow.com/questions/413477/is-there-a-good-valgrind-substitute-for-windows — jlew, May 05 '11 at 17:02

score 6 · Accepted Answer · answered May 05 '11 at 17:00

6

Compile with /RTCs, which enables stack frame run-time error checking. See /RTC (Run-Time Error Checks).

answered May 05 '11 at 17:00

RichieHindle

272,464
47
358
399

Is it possible to use /RTCs in release build? – Maanu May 05 '11 at 17:12
disabling optimization is enough for using /RTC in release ? – cprogrammer Nov 08 '11 at 14:57

score 0 · Answer 2 · answered May 05 '11 at 16:59

Does the corruption always happen in the same place? If so, you can easily use your debugger to set a watchpoint to detect writes at that location and see who's doing the corruption. Sometimes analyzing the data that corrupted the stack can also help you out - if it's a string, for example, you might be able to narrow down the code that's writing it.

detect stack corruption

2 Answers2