Visual Studio 2015: Using The Remote Debugger

Intro

Most of this write up just summarizes what's talked about in this video: Visual Studio - How to Attach Debugger to a Remote Server
This Microsoft web page documents how to install and run the remote debugger: VS Remote Debugging Installation And Running

Prerequisites

  1. The Visual Studio Remote Debugger for 2015 is called rtools_setup_x64.exe
  2. To properly debug on a remote machine, you will need debug symbols for your code.

Install And Run The Remote Debugger

  1. Find rtools_setup_x64.exe, and install it on the remote server.
  2. After install, go to the Start menu and run Remote Debugger.
  3. You may have to configure the firewall, this can be done through the Remote Debugging Configuration dialog that the Remote Debugger launches.  Allow everything.
  4. Once the remote debugger is running, go to the Tools menu and select Options.
  5. The port will probably be 4020, change this to 4016.  I could not get 4020 to work.
  6. Tick No Authentication and Allow any user to debug.
  7. Click OK.

    NOTE: These settings are not saved between runs of the Remote Debugger.  You have to do this every time!


     
  8. You will now see the name of your server and port in the remote debugger dialog.


     
  9. Launch the application you want debugged.
  10. Now go to your local machine to connect to this remote machine.

Connect To Remote Machine From Local Machine

  1. Launch a local version of Visual Studio 2015 and load the solution you'd like to debug on the remote machine.
  2. Choose Debug -> Attach to Process...
  3. For Transport: choose Remote (no authentication)
  4. For Qualifier: type the name of the server and port as shown in the remote debugger UI on the remote machine.  For instance: LA1DPTCNSVR103:4016
  5. Click Find...
  6. Your remote server should be listed in the Remote Connections dialog, click its entry then click the Select button.

  7. Find the process which you would like to debug.  Select it and select Attach.


     
  8. You should now be attached to the remote process and can set breakpoints and debug using your local Visual Studio debugger.


Comments

Post a Comment

Popular posts from this blog

FFMPEG Deinterlacing Modes

FFMPEG has multiple supported deinterlacing filters.  Here they are: 10.14 bwdif Deinterlace the input video ("bwdif" stands for "Bob Weaver Deinterlacing Filter"). Motion adaptive deinterlacing based on yadif with the use of w3fdif and cubic interpolation algorithms. It accepts the following parameters: mode The interlacing mode to adopt. It accepts one of the following values: 0, send_frame Output one frame for each frame. 1, send_field Output one frame for each field. The default value is send_field. parity The picture field parity assumed for the input interlaced video. It accepts one of the following values: 0, tff Assume the top field is first. 1, bff Assume the bottom field is first. -1, auto Enable automatic detection of field parity. The default value is auto. If the interlacing is unknown or the decoder does not export this information, top field first will be assumed. deint Specify which frames to deinterlace. Accept ...
Read more

Remote debugging with GDB and GDBServer on Alpine and Visual Studio Code

Skip to end of metadata o to start of metadata gdb and gdbserver can be used in combination to provide debugging capabilities over the network.   gdbserver  is run on the machine you want to debug.   gdb  is run on the machine you want to debug from, usually your local machine. More  here . Before we get started, we need some software.  Alpine 3.8 will be the gdbserver. NFS We will be using nfs (Network File System) to mount a remote directory and have it look like a local directory.  We will cd to the nfs mounted directory which contains the program we want to debug before we launch gdb.  This way the program and symbols will match.  gdb will be running on your local client, but it will be launched when in a directory on the gdbserver's system. More than you wanted to know about  nfs . To set up nfs, you will need nfs software on your server and your client. SERVER  (Your Alpine machine) - Ad...
Read more

Build FFMPEG for Windows Using Visual Studio Toolchain

FFMPEG for Windows is built under MinGW or Cygwin.  We will be using MinGW. You may need ZLib, the ZLib provided with MinGW does not come with a .a file for some reason.  You can find ZLib at  https://zlib.net/ Build Zlib so that you get zlib.lib. Follow this page:  https://trac.ffmpeg.org/wiki/CompilationGuide/MSVC NOTE: When following the instructions on the above page, they only give a configure command for a release version, which is: ./configure --target-os=win64 --arch=x86_64 --toolchain=msvc If you want to do a full debug build, try this: ./configure --target-os=win64 --arch=x86_64 --toolchain=msvc --extra-cflags=" -EHa -nologo -D 'DEBUG' -D 'WINDOWS' -D 'HAVE_STRUCT_TIMESPEC' -D 'API_EXT_PARAM_LIST'" --enable-debug --disable-stripping --disable-optimizations --disable-cuda --disable-cuvid --disable-d3d11va --disable-dxva2 --disable-nvenc --disable-vaapi --disable-vdpau You should now be ready to use ffmpeg in a...
Read more