WingEditor's debugger environment only works with projects, so, before using debugger, a project has to be created. For details on project, please see How to Create a Project.
Also, the project has to be set as the current project. To set the project as the current project, go to Build menu, and select Setting.
To user debugger effectively, all classes should be compiled
with -g.
Go to Build menu, and select Debug, WingEditor will use the current window as source browsing window, and bring up a debugger window which consists of debugger button bar, user output console, debugger message console, and command/parameters input field.
The button bar in your current window will be changed to hold some debugger buttons, and the file under editing has been changed to the Main Class file, and stop in the main method.
In the current window, the button bar holds 10 debugger buttons,
In the debugger window, there are 4 sections,
1. Button Bar
It holds 8 buttons for debugging,
2. User Application Console
This console is used as the program's standard output console, i.e., if the application has any output to the System.out, they will appear in this console.
3. Debugger Console
This console will be used as debugger's console. All debugging message will be printed in this console.
4. Input Text Field
Users can execute all the jdb commands by just entering them in this field. This text field is also used as input field for some debugger buttons (Stop in, Stop at Clear, print) which requires parameters.,