When you check a session in the Finish Debugging Sessions dialog box, the the session is exited and disappears from the Sessions tab when you click OK.
If a session is not checked, the session becomes persistent and the Action on Finish property, which you set in the Sessions tab of the Debugger window, determines the action to take. If you set the Action on Finish property to Finish Session, the debugged VM exits if it was launched by the debugger or disconnects if it was attached. The session state becomes "not running." When you start the debugger again, the process is launched or attached by the debugger.
If you set the Action on Finish property to Hide Session and Listen, the debugged VM does not exit or disconnect, but remains running. No information related to this process is displayed and debug commands are disabled. Breakpoints remain set in the debugged VM and if one is hit, the session's state changes to "stopped on breakpoint" and the debugger starts. When you start the debugger, the session state changes to "running."
Hiding a session is useful if you have started a complex application by the debugger (for example, a server) and you want to stop debugging, but not execution of the application (so that you can modify the client sources and debug the application later).
See also | |
---|---|
Modifying Session Properties |