Introduction to the Debug Viewer


The Toolkit includes a simple debug/trace facility. It is for use by developers and does not have the features necessary to support debugging of customer problems. The viewer lets you filter out messages by type and developer-defined codes.

The abstract class LogFile provides an API for printing messages to the Debug Viewer. It allows you to classify messages by severity code and type. You are responsible for writing the message that get sent to the Debug Viewer and for defining messages types. The toolkit supplies the severity codes. You assign the appropriate code to individual messages.

The Debug viewer wraps long messages. It can process line feeds (\n) and tabs (\t), but ignores other control characters. The viewer can display a maximum of about 28KB of text. After that point, it begins throwing out the oldest messages as new messages get printed. If you have a console running, the messages removed from the viewer are sent to the console.

Only one instance of the Debug viewer can run at a time. Once it is running, additional invocations have no effect. Using the Debug viewer can affect the performance of Sybase Central. If you close the viewer, all structures related to it are destroyed. The messages generated by the application don't go anyplace. You cannot start the Debug viewer again until you restart Sybase Central. Any performance loss created by the viewer is regained when you close it.


Related Topics:
 Debug viewer window