The primary purpose of a stack trace is to be used in debugging to help developers locate the exact line of code and the sequence of function calls that led to a specific error, exception, or crash.
I debugged a crash of vmr which occurred while building fsharp repo on s390x. Looking at the crash, the stack had overflowed. I had not seen such an overflow on x64/arm64 (using CoreCLR). Looking ...
description: Use the Call Stack window in the Visual Studio integrated development environment (IDE) to view the function or procedure calls that are currently on the stack. # View the call stack and ...
Some results have been hidden because they may be inaccessible to you
Show inaccessible results