File: stepping.html

package info (click to toggle)
jswat 1.7-2
  • links: PTS
  • area: contrib
  • in suites: etch, etch-m68k
  • size: 5,656 kB
  • ctags: 3,210
  • sloc: java: 24,683; xml: 130; makefile: 59; sh: 21
file content (67 lines) | stat: -rw-r--r-- 2,205 bytes parent folder | download | duplicates (2)
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
54
55
56
57
58
59
60
61
62
63
64
65
66
67
<!DOCTYPE html PUBLIC "-//IETF//DTD HTML 2.0//EN">

<html>
  <head>
    <meta name="generator" content=
    "HTML Tidy for Linux/x86 (vers 1st February 2002), see www.w3.org">

    <title>Stepping Through Code</title>
  </head>

  <body>
    <h3>Stepping Through Code</h3>

    <p>Stepping in source code executes just one instruction or line of
    code in the debuggee at a time. This is useful for finding exactly
    where a particular condition occurs in the code. The actions
    described below are accessible via the named commands as well as
    through the &quot;Step&quot; menu items.</p>

    <h4>Operations</h4>

    <p>There are several commands for stepping through source code.
    They are described as follows.</p>

    <dl>
      <dt><code>step</code></dt>

      <dd>Step a single line of source code, going <em>into</em> method
      calls, if any. That is, if there is a method call being made,
      execution will be halted at the top of that new method.</dd>

      <dt><code>next</code></dt>

      <dd>Step a single line of source code, going <em>through</em>
      method calls, if any. That is, it runs the method at full speed
      rather than stepping into it.</dd>

      <dt><code>stepi</code></dt>

      <dd>Step a single instruction, going <em>into</em> method calls,
      if any.</dd>

      <dt><code>nexti</code></dt>

      <dd>Step a single instruction, going <em>through</em> method
      calls, if any.</dd>

      <dt><code>step out|up</code></dt>

      <dd>Returns to the line that invoked the current method. This is
      identical to the &quot;finish&quot; operation found in other
      debuggers.</dd>
    </dl>

    <h4>Exclusion filters</h4>

    <p>At some point or another you will single-step into the Java core
    classes. This will happen often enough that you wish you could
    avoid stepping into such classes. Fortunately, JSwat provides the
    <code>exclude</code> command for just this purpose. You can add
    individual classes and entire packages to the list of class
    filters. During single-stepping, the debugger will not step into
    these classes. See the exclude command help for more
    information.</p>
  </body>
</html>