1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
|
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta name="generator" content=
"HTML Tidy for Linux/x86 (vers 1st February 2002), see www.w3.org">
<title>Capturing Debugger Messages</title>
</head>
<body bgcolor="#ffffff">
<h2>Capturing Debugger Messages</h2>
<h3>Debugger Messages</h3>
<p>Debugger messages are those messages seen in the JSwat main
window whenever a command or action is performed. Each time a
breakpoint is hit or a single step is performed, a message is
printed to the window. Normally these messages go to a text area
within the JSwat window. This text area grows indefinitely until
JSwat is terminated. A scroll bar on the side of the text area
allows you to scroll up to see earlier messages. The text area also
has a popup menu that allows copying selected text to the system
clipboard.</p>
<h3>Capturing Messages</h3>
<p>JSwat provides a means for capturing the messages. Using the
"Capture Messages" action found in the
"Options" menu (as of 12/27/00) you can set the messages
to also print to JSwat's standard output stream (the console
that started JSwat) and/or to a named file. In the dialog that
appears after selecting "Capture Messages" you may check
the "Capture to stdout" or "Capture to file"
options. If you select the "Capture to file", be sure to
enter a filename in the text field at the bottom of the dialog.</p>
<p>To turn off the message capturing, simply bring up the same
"Capture Messages" dialog and uncheck the checked
options. If you only wish to change the name of the file which is
catching the messages, you may simply type a new name into the
dialog and press okay. The previous file will be closed and the new
file will be created. Make sure the "Capture to file"
option is checked before you press Ok.</p>
<p>Note that when capturing to file the messages do not flush to
the file immediately. Turning off the file capture will cause the
buffers to be flushed to disk. <em>(I would have preferred the
contents be flushed immediately but it does not seem to
work.)</em></p>
</body>
</html>
|
