4 ms·
How large was the stack dump? I'm impressed you identified it this quickly considering the time it would take to get this to disk.
by skeletonjelly 10y ago
How large was the stack dump? I'm impressed you identified it this quickly considering the time it would take to get this to disk.
- Nick-Craver 10y agoWe have an internal tool where we can dump stack traces almost instantly by attaching to a running process. We can't open source it due to using Microsoft lab code which was never licensed itself. However, clrmd (https://github.com/Microsoft/clrmd https://github.com/Microsoft/clrmd and https://www.nuget.org/packages/Microsoft.Diagnostics.Runtime https://www.nuget.org/packages/Microsoft.Diagnostics.Runtime) means an open source version is hopefully on the horizon. As an example, here's the result of me piddling in 2 hours with LinqPad: https://gist.github.com/NickCraver/d6292c0c7f93767686e8c5c89ed45c54 https://gist.github.com/NickCraver/d6292c0c7f93767686e8c5c89... Process attachment is in the clrmd roadmap, but isn't stable yet.
- skeletonjelly 10y agoAwesome. Thanks for the response, love your work Nick.