Background and Motivation
Hello,
As the title says, I found a way to recover traces that are affected by the 100-stack-frame limit. I pulled this off by carefully recovering the missing call stacks from a known good previous call stack sample. This logic is better explained in my blog post: https://dfamonteiro.com/posts/dotnet-trace-final-fix/.
And here's the fork with the changes detailed in my blog post: https://github.com/dfamonteiro/daniel-trace
I thought you might find this an interesting improvement opportunity to dotnet-trace
Background and Motivation
Hello,
As the title says, I found a way to recover traces that are affected by the 100-stack-frame limit. I pulled this off by carefully recovering the missing call stacks from a known good previous call stack sample. This logic is better explained in my blog post: https://dfamonteiro.com/posts/dotnet-trace-final-fix/.
And here's the fork with the changes detailed in my blog post: https://github.com/dfamonteiro/daniel-trace
I thought you might find this an interesting improvement opportunity to
dotnet-trace