Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GetProcessInfo command no process arguments on non-Windows while suspended #885

Open
jander-msft opened this issue Sep 21, 2021 · 1 comment
Labels
bug Something isn't working

Comments

@jander-msft
Copy link
Member

jander-msft commented Sep 21, 2021

If a .NET 5+ runtime is suspended and a GetProcessInfo command is issued over the diagnostic pipe, then the CommandLine only contains the process name on Unix operating systems, e.g.:

/__w/1/s/.dotnet/dotnet

If the GetProcessInfo command is issued immediately after resuming the runtime, the same data is reported (only the process name).

If the GetProcessInfo command is issued sometime AFTER the runtime is resumed, then it returns the property command line, e.g.:

/__w/1/s/.dotnet/dotnet /__w/1/s/artifacts/bin/Microsoft.Diagnostics.Monitoring.UnitTestApp/Release/net5.0/Microsoft.Diagnostics.Monitoring.UnitTestApp.dll AsyncWait

@jander-msft jander-msft added the bug Something isn't working label Sep 21, 2021
@jander-msft jander-msft changed the title GetProcessInfo command no process arguments on .NET 5 on non-Windows while suspended GetProcessInfo command no process arguments on non-Windows while suspended Sep 21, 2021
@jander-msft
Copy link
Member Author

Corresponding runtime issue: dotnet/runtime#59439

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant