search

microsoft / vscode-cpptools

Official repository for the Microsoft C/C++ extension for VS Code.
Other
5.51k stars 1.55k forks source link

Feature Request: Remote Debugging for cppvsdbg #1098

Open paulolamas opened 7 years ago

paulolamas commented 7 years ago

I debug my applications on a Remote Test PC because I have additional hardware attached to that PC that I can't attach to my Development PC. I currently use Visual Studio to do that. I take a copy of "C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\Remote Debugger\x86\" and run "..\Remote Debugger\x86\msvsmon.exe" on my Test PC. Then I attach to my application using VS->"Transport"->"Remote (no authentication)". No authentication connection is OK for me because I'm on a private network. I would like to be able to do something similar with vscode so that my whole development environment is on vscode using the cpptools extension. My application is built with an internal build environment and I can only use msvc as the compiler, so I can't switch to "cppdbg"

DvoryankinEvgeny commented 4 years ago

Hello @pieandcakes Is it still impossible to remotely debug C++ application using cppvsdbg? I have the same situation like @paulolamas. My application builds by cl.exe and I have to debug my application on the VM because of the risk of OS corruption. I'm using vscode for editing code and switching to VS for debugging is so annoying.

pieandcakes commented 4 years ago

@DvoryankinEvgeny It isn't supported as of now. We suggest for now using Visual Studio Community Edition if you want to do remote Visual C++ debugging until support has been added.

DvoryankinEvgeny commented 4 years ago

@DvoryankinEvgeny It isn't supported as of now. We suggest for now using Visual Studio Community Edition if you want to do remote Visual C++ debugging until support has been added.

You broke my heart :( Thank you for answer :)

dwilliamson commented 1 year ago

I wish to use VSCode for Driver development on a Target Machine that contains custom hardware that is continuously under development. So far everything has been good, until I got to Remote Debugging.

HW/Driver development is very chaotic, requiring constant reboots and remote debugging of the drivers you are developing.

Using the existing VSCode Remote SSH solution is painful for this as you constantly disconnect and can't browse your source while the driver is under debug. There are many occasions in the day where the Remote extension can't reconnect and you have to reload your window.

Granted, this is nowhere near as painful as developing on the Target Machine itself, but it's worlds away from the Visual Studio experience of being able to connect to a remote application.