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
|
<!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>Catch Exceptions</title>
</head>
<body bgcolor="#ffffff">
<h2>Catch Exceptions</h2>
<h3>Catching Exceptions</h3>
<p>JSwat supports catching exceptions. This includes exceptions
that are caught in the Java code running in the debuggee VM and
exceptions that are not caught.</p>
<p>The <code>catch</code> command can be used to create an
exception catch. There is also a dialog box available from the
"Breakpoints" menu. Both the command and the dialog
require the name of the exception to be caught. This must either be
a fully-qualified class name or a wild-carded class name (i.e. has
a '*' either at the beginning or end of the name).</p>
<p>Exception breakpoints can have both class and thread filters.
See the <a href="breakpoints.html">breakpoints help</a> for
the section on setting up filters. The class filters apply to the
class that is throwing the exception.</p>
<p>A single exception may be thrown multiple times. JSwat does not
distinguish this case and so it may appear that more than one
exception is being caught when in fact it is only one that has been
rethrown.</p>
<p>JSwat always creates an invisible exception breakpoint for all
uncaught exceptions. This breakpoint cannot be removed or modified
as it is not visible to the user.</p>
</body>
</html>
|
