To help us better track down a bug you are reporting, it is often helpful if you also include the system state of the HotJavaTM Browser when the bug occurs. In order to do this, a log of the HotJava session must be recorded.
On Solaris systems: To enable logging, start the HotJava Browser from a command line with the -log logfile option. For example, to send log comments to the file /tmp/log, you would start the HotJava Browser with this command: hotjava -log /tmp/log. To send the log comments to the window where you started the HotJava Browser, use: hotjava -log /dev/tty. Alternatively, you can set the environment variable HOTJAVA_LOG to specify the log file.
To get the HotJava system state, the HotJava Browser must be running in the foreground. If you started the HotJava Browser with the command hotjava -log logfile &, the & put HotJava into the background. In this case, type fg to bring the HotJava process into the foreground.
Once you are running the HotJava Browser with logging enabled and as a foreground process, you can get the state on Solaris systems by typing Ctrl-\ in the window that the HotJava Browser was started in.
On Windows systems: Logging is automatically enabled if you start the HotJava Browser using hotjava_g.exe. This gives you console output, and you can type Ctrl-BREAK to get a stack trace when reporting bugs.
If you prefer to have the output go to a log file, either set the environment variable HOTJAVA_LOG to specify the log file, or run hotjava_g.exe with the -log logfile option.