question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Debugger: Improve the error message when vscode attempt to attach to dotnet process with mismatched privilege

See original GitHub issue

Environment data

dotnet --info output: VS Code version:1.2.1 C# Extension version:1.1.7

Steps to reproduce

  1. Create a sample .dotnet core console application with following code:

    public static void Main(string[] args)
    {
        Console.ReadLine();
        Console.WriteLine("Hello World!");
    }
    
  2. Launch vscode with non-admin and open the project

  3. Launch command line with admin, and run the application “dotnet run”

  4. Set the target as “attach” and configure the process id of “dotnet”

  5. F5

    Expected behavior

Actually, when I did the testing, I was not aware of launching vscode with non-admin, I suppose this is not supported scenario, however I assume we should at least improve the error message,

  1. At least we should try to remove the internal error message "Unexpected CLRDBG output from command “-target-attach 8508”. " ?
  2. Is it possible to add some useful information similar like “vscode doesn’t have the sufficient permission to attach the process” if the permission of vscode and attached process is mismatched ?

Actual behavior

Error: No process with the specified id is currently running.

(This is VSDBGE_E_PROCESS_ID_NOT_FOUND)

Issue Analytics

  • State:closed
  • Created 7 years ago
  • Comments:13 (9 by maintainers)

github_iconTop GitHub Comments

1reaction
gregg-miskellycommented, Jul 24, 2017

@kroppt I reproduced your issue and I opened up https://github.com/OmniSharp/omnisharp-vscode/issues/1660 to track it. I hope to have a private out later today with the fix.

0reactions
gregg-miskellycommented, May 8, 2018

Lets see if we can fix this for 1.16, as several people have hit into it now.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Remote Debugging Errors and Troubleshooting
View links to common remote debugging errors in Visual Studio. Learn how to run the remote debugger as an administrator.
Read more >
Debugging in Visual Studio Code
One of the great things in Visual Studio Code is debugging support. Set breakpoints, step-in, inspect variables and more.
Read more >
Debugging configurations for Python apps in Visual Studio Code
Details on configuring the Visual Studio Code debugger for different Python applications.
Read more >
Access denied when attempting to run under the debugger.
Open Visual Studio and attempt to Debug the project on network share. When you get the access denied error, you should see new...
Read more >
Debugger Extension - Visual Studio Code
This is most easily achieved by running the debug adapter in server mode and configure VS Code to connect to it. In your...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found