Before you can debug a Yellow Box Java application, you must build the application with the proper debugging symbols and then run the Java Debugger, after which you can set breakpoints and begin debugging.
To debug "wrapped" frameworks of yours on Yellow Box for Windows systems, you must first install the debug versions of the Yellow Box libraries (DLLs).
If you have a Mac OS X system, you do not need to complete this task. Skip ahead to the next task, Build for Debugging .
Select the debug item from the Target pop-up menu, as shown in the illustration below:
The "make clean" button on the Build panel looks like a broom:
When you have built the project and have an executable containing symbols understood by jdb , run the Java Debugger from Project Builder. Project Builder knows which debugger to run, based on the type of executable it is debugging.
For the following exercise, assume that you are debugging a program containing only (or mostly) Java code, such as Temperature Converter.
The Java Debugger is automatically selected when your project contains Java code. The gdb debugger is also selected if the "Use GDB when debugging Java programs" preference (in the Debugging display of the Preferences panel) is selected. If you do not want gdb active when you debug Java programs, turn off this preference.
The Java Debugger starts up and displays its "JavaDebug>>" prompt. Because the Java VM is an interpreter, you do not need to suspend the Java Debugger to perform tasks such as setting breakpoints. You can, however, suspend and resume the Java Debugger if you wish. The Suspend/Continue button looks like this in Suspend mode (in the setting of its neighboring controls):
And in Continue mode the button looks like this: