堆栈溢出后，Visual Studio 2008显示完整的堆栈跟踪

Question

I have a running C++ project that has had a stack overflow whilst I was running it under the debugger within the IDE.

Visual Studio 2008 has taken it upon itself to truncate the stack trace of the overflowing thread (well hey if we're gonna do that why check for overflows at all?).

Is there some view option or debugging option that will show me the root of this thread's calls?

So in essence apart from offering me reasons why a stack trace can be corrupted etc (shall I disable my AV and run memtest86 as well?) does anyone have ACTUAL INFORMATION about the truncation of stack traces in Visual Studio 2008?

Answer 1

The simple solution is to keep your stack small enough from the start, so that the stack overflow happens earlier. You didn't want one megabtyte of repeated functions anyway.

Answer 2

If you want to have a big stack AND avoid stack overflow due to some simple recursion bug, use TLS: http://msdn.microsoft.com/en-us/library/windows/desktop/ms686749(v=vs.85).aspx .

Allocate one slot when the process starts and then increment the value of the slot using TlsGetValue and TlsSetValue and then check if it's exceeded, then break into the debugger or do some other "pause" in your supposedly faulty function.

It won't work for 3rd party code without hacks, but it worked well for me to work around the limitation and also being pretty light.