On Windows if an application crashes with a stack overflow and a dump is collected, looking at it in both Visual Studio and windbg gives little clue about the callstack which caused the overflow.
The desired behavior is that both VS and windbg should prominently show that a StackOverflow occured and show the callstack frames that ran recursively to cause the overflow.
On Windows if an application crashes with a stack overflow and a dump is collected, looking at it in both Visual Studio and windbg gives little clue about the callstack which caused the overflow.
For repro and observed behavior, see https://github.com/dotnet/diagnostics/issues/3506. #3506 tracks improving the documentation, this issue tracks improving the actual product experience.
The desired behavior is that both VS and windbg should prominently show that a StackOverflow occured and show the callstack frames that ran recursively to cause the overflow.