{"id":38,"date":"2006-08-03T12:30:08","date_gmt":"2006-08-03T17:30:08","guid":{"rendered":"http:\/\/www.nynaeve.net\/?p=38"},"modified":"2019-12-13T17:41:40","modified_gmt":"2019-12-13T22:41:40","slug":"remote-debugging-review","status":"publish","type":"post","link":"http:\/\/www.nynaeve.net\/?p=38","title":{"rendered":"Remote debugging review"},"content":{"rendered":"

Over the past week or two, I’ve written about some of the various remote debugging options available to you through the Debugging Tools for Windows<\/a> (DTW) package.\u00c2\u00a0 I’ve covered most of the major debugging mechanisms available at this point and given brief descriptions of their strengths and weaknesses.<\/p>\n

Here’s an indexed listing of the posts on this topic so far:<\/p>\n

    \n
  1. Overview of WinDbg remote debugging<\/a><\/li>\n
  2. Remote debugging with remote.exe<\/a><\/li>\n
  3. Remote debugging with KD and NTSD<\/a><\/li>\n
  4. Remote debugging with -server and -remote<\/a><\/li>\n
  5. Reverse debugging -server and -remote<\/a><\/li>\n
  6. Securing -server and -remote remote debugging sessions<\/a><\/li>\n
  7. Remote debugging with process servers (dbgsrv)<\/a><\/li>\n
  8. Activating process servers and connecting to them<\/a><\/li>\n
  9. Remote debugging with kdsrv.exe<\/a><\/li>\n
  10. Remote debugging review<\/a><\/li>\n<\/ol>\n

    At this point, you should be able to use all of the above remoting mechanisms in their basic usage cases.\u00c2\u00a0 There are a couple of obscure features that I did not cover, such as doing -server\/-remote over serial ports, but between my posts and the documentation you should be able to figure out what to do if you ever find a use for such estorica (let me know if you do!).\u00c2\u00a0 What remains to be told is some general advice on which remoting mechanism is the best for a particular problem.<\/p>\n

    In general, the most important factors in choosing a remoting mechanism are:<\/p>\n