Starting a Debug Session

To start a new debugging session, select Debug | Start Process which will launch your Java program from within BugSeeker using the current Java runtime specified in the Project's Runtime tab. Depending on your project's current project type, the Start Process command may do several things. If your project type is Application, Start Process will launch your Java program. If your project type is Applet, Start Process will launch the appletviewer and direct the appletviewer to use the HTML file containing an applet tag. If your project type is Servlet, Start Process will launch the JSWDK's test webserver so that you will be able to open your web browser and navigate to the page hosting your serlvet. If your project type is Remote, the Start Process command will be disabled.

Remote Debug Sessions

Another way to start a debug session is to launch your Java program, Java plugin engine, Java web server, Java application server, etc. separately after supplying the property JPDA JVM debug options and then using BugSeeker's remote debugging capabilities to connect to this debug JVM. This is a very flexible and powerful way of initiating a debugging session and is often the only way in which you can debug your program running in your desired runtime configuration.

To have BugSeeker attach to a remote JVM running in debug mode, select Debug | Remote | Attach and follow the instructions displayed in the Remote Debug Attach dialog carefully.

To have BugSeeker listen for one or more incoming debug connections from remotely running JVMs, select Debug | Remote | Listen and follow the instructions display in the Remote Debug Listen dialog carefully.

Please see the Remote Debugging section of the manual for more information.