Controlling a Process Server Session

Once the remote session has been started, the smart client can be used as if it were debugging a target application on a single machine. All commands will behave as they would in this situation, except that paths are relative to the smart client's computer.

Using WinDbg as a Smart Client

After WinDbg is started as a smart client for a user-mode process server, it will remain attached to the process server permanently. If the debugging session is ended, the File | Attach to a Process menu command or the .tlist (List Process IDs) command will display all processes running on the computer running the process server. WinDbg can attach to any of these processes.

The File | Open Executable command cannot be used. A new process can only be spawned if it is included on the WinDbg command line.

In this situation, WinDbg will not be able to debug processes on the computer where it is running, nor will it be able to start a kernel debugging session.

Ending the Session

CDB or WinDbg can exit or end the debugging session in the normal fashion. See Ending a Debugging Session in WinDbg for details. The process server will remain in operation and can be re-used as many times as desired. (It can also be used by for any number of simultaneous debugging sessions.)

The process server can be terminated from either computer. To terminate it from the smart client, use the .endpsrv (End Process Server) command. To terminate the process server from the computer it is running on, use Task Manager to end the dbgsrv.exe process.

Send comments about this topic to Microsoft