dotnet-stack report hangs when run in a directory without write permissions

[noahfalk]

Description

The dotnet-stack report command attempts to create a temporary trace file in the current directory (https://github.com/dotnet/diagnostics/blob/main/src/Tools/dotnet-stack/ReportCommand.cs#L41 + https://github.com/dotnet/diagnostics/blob/main/src/Tools/dotnet-stack/ReportCommand.cs#L85) which implicitly assumes the current directory is writable. When the tool is run in a directory that isn't writable it produces no output and becomes unresponsive.

Configuration

diagnosing an app on .NET 6

E:\temp>dotnet-stack --version
6.0.320703+c1d79351e6181a4daa61e38e8df6daf791b33401

Regression?

Didn't check but probably not

fyi @josalem

[noahfalk]

Btw, the way I hit this is using the "Developer Command Prompt for VS" which defaults to a path like this: "C:\Program Files (x86)\Microsoft Visual Studio\2017\Community" which isn't writable.