Fix SSH attach on a clean machine#1444
Merged
andrewcrawley merged 1 commit intomicrosoft:mainfrom Mar 1, 2024
Merged
Conversation
Attaching to a C# process running on a brand-new Linux VM was failing with an error about being unable to create or access the `.vs-debugger` folder on the remote host. After investigating, this is due to a behavior change in liblinux - previously, the call to `IRemoteFileSystem.Stat()` would fail if the file didn't exist, but it now returns a valid object that you can query to determine that the file doesn't exist. Workaround: manually create the `.vs-debugger` folder on the remote host. Once it exists, debugging works.
WardenGnaw
approved these changes
Mar 1, 2024
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Attaching to a C# process running on a brand-new Linux VM was failing with an error about being unable to create or access the
.vs-debuggerfolder on the remote host. After investigating, this is due to a behavior change in liblinux - previously, the call toIRemoteFileSystem.Stat()would fail if the file didn't exist, but it now returns a valid object that you can query to determine that the file doesn't exist. I updated the logic accordingly.Workaround: manually create the
.vs-debuggerfolder on the remote host. Once it exists, the remote debugger will deploy successfully.