ghost
commented
10 months ago Tagging subscribers to this area: @tommcdon See info in area-owners.md if you want to be subscribed.
Issue Details
## Background and Motivation We make tools that analyze dumps with managed memory in them to automatically find common development issues. For Linux, dotnet-dump is currently the tool we use to create dumps ## Proposed Feature For a managed process that host plug ins, or other apps the command line often contains the actual binary / team / function that process is performing. I.e. `pwsh` or `dotnet` processes doesn't tell you a lot about who should be consuming the data from the dump. The arguments to those processes have all the information. Can we capture the command line arguments to the dotnet process in the ELF headers so we can be specific about determining which function the process was asked to perform.
| Author: | nschuessler |
|---|---|
| Assignees: | - |
| Labels: | `enhancement`, `area-Diagnostics-coreclr`, `needs-area-label` |
| Milestone: | 9.0.0 |
tommcdon
Background and Motivation
We make tools that analyze dumps with managed memory in them to automatically find common development issues. For Linux, dotnet-dump is currently the tool we use to create dumps
Proposed Feature
For a managed process that host plug ins, or other apps the command line often contains the actual binary / team / function that process is performing. I.e.
pwshordotnetprocesses doesn't tell you a lot about who should be consuming the data from the dump. The arguments to those processes have all the information.Can we capture the command line arguments to the dotnet process in the ELF headers so we can be specific about determining which function the process was asked to perform.