anjuta-common 2:3.10.2-0ubuntu2 / usr / share / help / C / anjuta-manual / debug-step.page

This file is indexed.

/usr/share/help/C/anjuta-manual/debug-step.page is in anjuta-common 2:3.10.2-0ubuntu2.

This file is owned by root:root, with mode 0o644.

The actual contents of the file can be viewed below. 

  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
 68
 69
 70
 71
 72
 73
 74
 75
 76
 77
 78
 79
 80
 81
 82
 83
 84
 85
 86
 87
 88
 89
 90
 91
 92
 93
 94
 95
 96
 97
 98
 99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
<page xmlns="http://projectmallard.org/1.0/"
      type="topic" style="task"
      id="debug-step">

  <info xmlns:facet="http://projectmallard.org/facet/1.0/">
    <facet:tag key="all-pages" value="whatever"/> <!--Include page in index-->
    <link type="guide" xref="debug-execute" group="first"/>
    <revision pkgversion="3.0" version="0.1" date="2011-03-27" status="incomplete"/>
    <desc>
      Stopping and continuing.
    </desc>
    <credit type="author">
      <name>Sébastien Granjoux</name>
      <email>seb.sfo@free.fr</email>
    </credit>
    <credit type="editor">
      <name>Philip Chimento</name>
      <email>philip.chimento@gmail.com</email>
    </credit>
  </info>

  <title>Stop and step</title>

  <p>Like a video editing session, the program can be executed in slow motion
   with the ability to go forward, pause, stop, and so on.
   This is essential for tracking program behavior. You cannot go
   backward yet, though.</p>

  <section>
    <title>Step in</title>

    <steps>
      <item>
        <p>From the <gui>main menu</gui>, select <guiseq><gui>Debug</gui>
        <gui>Step In</gui></guiseq> or press <key>F5</key> or
        click on the <gui>Step In</gui> icon in the toolbar.</p>
      </item>
    </steps>

    <p>Single stepping executes only one statement of the program (from the
    place where it has stopped) and then returns control. If the statement
    that is executed contains one function, the debugger tries to step
    inside the functions (in the sequence in which the functions are executed).
    Once the statement is executed and control is passed back, you can study
    your program's state.</p>

    <note style="advanced">
     <p>If the <gui>Disassembly window</gui> has the focus when
     this command is selected, it executes only one assembler instruction.</p>
    </note>
  </section>


  <section>
    <title>Step over</title>

    <steps>
      <item>
        <p>From the <gui>main menu</gui>, select <guiseq><gui>Debug</gui>
        <gui>Step Over</gui></guiseq> or press <key>F6</key> or
        click on the <gui>Step Over</gui> icon in the toolbar.</p>
      </item>
    </steps>

    <p>Stepping over is similar to stepping except that it does not stop
    inside any function in the statement being executed.</p>

    <note style="advanced">
      <p>If the <gui>Disassembly window</gui> has the focus when
      this command is selected, it executes only one assembler instruction, except
      if that instruction is a call to a subroutine, in which case the program stops
      when the subroutine is completed.</p>
    </note>
  </section>


  <section>
    <title>Step out</title>

    <steps>
      <item>
        <p>From the <gui>main menu</gui>, select <guiseq><gui>Debug</gui>
        <gui>Step Out</gui></guiseq> or press <keyseq><key>Shift</key><key>F5</key></keyseq> or
        click on the <gui>Step Out</gui> icon in the toolbar.</p>
      </item>
    </steps>

    <p>Stepping out executes the current function until it returns to the calling
    function.</p>
  </section>


  <section>
    <title>Run and continue</title>

    <steps>
      <item>
        <p>From the <gui>main menu</gui>, select <guiseq><gui>Debug</gui>
        <gui>Run/Continue</gui></guiseq> or press <key>F4</key> or
        click on the <gui>Continue</gui> icon in the toolbar.</p>
      </item>
    </steps>

    <p>This command restarts the program and lets it run until a breakpoint is encountered or
    the program exits.</p>
  </section>

  <section>
   <title>Run To</title>

    <steps>
      <item>
        <p>From the <gui>main menu</gui>, select <guiseq><gui>Debug</gui>
        <gui>Run to Cursor</gui></guiseq> or press <key>F8</key> or
        click on the <gui>Run to</gui> icon in the toolbar.</p>
      </item>
    </steps>

    <p>This restarts the program and lets it run until the line or the
    address (if the <gui>Disassembly window</gui> has the focus) at
    the cursor is reached.</p>
  </section>
  
  <section>
   <title>Stopping the Program</title>

    <steps>
      <item>
        <p>From the <gui>main menu</gui>, select <guiseq><gui>Debug</gui>
        <gui>Pause Program</gui></guiseq> or
        click on the <gui>Pause</gui> icon in the toolbar.</p>
      </item>
    </steps>

   <p>This interrupts the program and returns control to the debugger, allowing
   you to perform debugging tasks, like inspecting data or adding breakpoints.</p>
  </section>


</page>

APT Browse - Built by Thomas Orozco.