Once you have determined the cause of your bug, you will probably want to go fix it immediately. Because BugSeeker does not currently support the feature where you can fixing and compile the code and continue debugging without stopping the program, you will need to stop the current debugging session, apply your fixes, recompile, and start the debugging session again. To stop a debugging session, which you may do so when the current session is either paused or running, choose Debug | Stop.
Closing a project that has active sessions or exiting BugSeeker will automatically stop all debug sessions and terminate all processes launching from within BugSeeker. For any processes being debugged remotely, BugSeeker will ask if you wish to terminate the remote VM or to let it continue running.
When a session is stopped, most debug tabs that are useful only when a session is active will be removed and all inspector windows open for this session will be closed. The only remaining debug tabs will be the Console tab so that you can review the console output and the Info debug tab which provides details about the debuggee's VM.