Improve scenarios where dump analyze commands spew lots of output
Open
dotnet-dump
enhancement
- Dominant language
- C++
- Stars
- 1.3k
- Forks
- 404
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 38
Description
With larger dumps, some of the `sos` commands are much harder to use as they spew lots of output and which can be hard to cancel. We could do a few things to improve the situation:
- Add ability to pipe dump analyze commands to stderr/stdout (this would also allow piping to something like `less`/`more`).
- Add a default paging experience when there's too much output (with the ability to stop paging and completely cancel the command).
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.