dotnet / dotnet/vscode-csharp

Debugger: Improve error message when attempt to attach a process which has already attached by another debugger

Open
#1,302 0 comments 0 reactions 0 assignees View on GitHub
Bug Debugger Debugger-Poachable OmniSharp
Dominant language
TypeScript
Stars
3.1k
Forks
737
Avg merge
18h 40m
Merged PRs (30d)
31

Description

## Environment data
`dotnet --info` output:
Server Machine:
OS: linuxmint17
VS Code version:1.10.2
C# Extension version: v1.8.0-beta2(https://github.com/OmniSharp/omnisharp-vscode/releases/tag/v1.8.0-beta2)
vsdbg: https://aka.ms/getvsdbgsh

Client Machine:
OS: centos7

## Steps to reproduce
1. Open attached folder with VSCode on Client and Server Machine.
[hwapp.zip](https://github.com/OmniSharp/omnisharp-vscode/files/830433/hwapp.zip)

2. Update the ".NET Core Remote Attach" configuration on launch.json file on Client Machine.
3. Launch hwapp process on Server Machine with VSCode.
4. Remote attached the server process.

## Expected behavior
Is it possible to improve the error message similar like "Attach to process fail, the process has already attached to a debugger".

## Actual behavior
Pop up an error message:
![errormessage](https://cloud.githubusercontent.com/assets/20184768/23745863/cd44e698-04f4-11e7-8736-f1b6600f16b8.PNG)

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.