Advanced Search
Welcome to Omgili,
Omgili (Oh My God I Love It ;) is a search engine for discussions. With Omgili you can find answers and solutions, debates, discussions, personal experiences, opinions and more... To learn more about Omgili click here.

This is a complete preview of the discussion as it was indexed by Omgili crawlers. Use this preview if the original discussion is unavailable.
Click here to view the original discussion.

best technique for launching a windbg user-mode remote debugging session

What is your favorite technique for launching a windbg user-mode remote debugging session?

Why is do you prefer this technique over other techniques?

(pros/cons) There are at least four different ways to do user-mode remote debug using windbg, as documented in the "Remote Debugging" section of the debugging tools for windows help file. run app on target then attach to it from the host windbg have the host windbg use remote.exe to launch the app on the target have the "smart client" host windbg launch the app on the target via a process server that is running on the target run a windbg instance on the target machine using the option "-server" to automatically start a server, then connect to the server from a 2nd machine.

Option 1 is my favourite because it is the simplest.

I get to launch the app in the normal way without worry about getting WinDbg to set the right working directory, pass any command line arguments, etc. Fortunately I've not run into any cases where this hasn't worked!

I tend to use option 4 (-server) because it is the only one that doesn't "pop" when you break into the kernel debugger long enough for the TCP connection to timeout.

But this is more complex and not fully satisfying.

So I'm looking for "best practices".




Omgili Home About FAQ Plugins Usenet