This file is indexed.

/usr/share/help/ja/anjuta-manual/debug-breakpoint.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
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
<?xml version="1.0" encoding="utf-8"?>
<page xmlns="http://projectmallard.org/1.0/" type="topic" style="task" id="debug-breakpoint" xml:lang="ja">

  <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="second"/>
    <revision pkgversion="3.0" version="0.1" date="2011-03-27" status="incomplete"/>
    <desc>
      Managing breakpoints.
    </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>ブレークポイント</title>

  <p>Breakpoints are used to stop the execution of the program at a particular
  point so that the state of the program can be examined at those locations.</p>

  <section>
    <title>Listing breakpoints</title>

    <steps>
      <item>
        <p>From the <gui>main menu</gui>, select <guiseq><gui>View</gui>
        <gui>Breakpoints</gui></guiseq> to open the <gui>Breakpoint</gui>
        window.</p>
      </item>
    </steps>

    <p>This view has the following columns:</p>
  
    <terms>
      <item>
        <title>位置</title>
        <p>ソース ファイルのブレークポイントの位置です。デバッガーによりブレークポイントが設定されると、そのブレークポイントがどの関数に含まれるか等の、追加情報を得ることができます。</p>
      </item>
      <item>
        <title>アドレス</title>
        <p>この項目にはデバッガーにより設定された、ブレークポイントのアドレスがセットされます。</p>
      </item>
      <item>
        <title>タイプ</title>
        <p>This always displays <gui>breakpoint</gui>. It will be used in a
        future release supporting different kinds of breakpoints.</p>
      </item>
      <item>
        <title>条件</title>
        <p>ブレークポイントの条件です。条件が設定されていない場合は何も表示されません。</p>
      </item>
      <item>
        <title>通過する回数</title>
        <p>デバッガーが実行されていない場合、ブレークポイントを通過する回数が表示されます。設定されていない場合は、0が表示されます。</p>
        <p>デバッガーが実行中の場合、通過する回数が0のときはプログラムがそのブレークポイントを通過した回数が表示されます。通過する回数に0以外を設定した場合は、通過した回数と右側に設定した回数が表示されます。</p>
      </item>
      <item>
        <title>状態</title>
        <p>This is the state of the breakpoint. It may be</p>
        <terms>
          <item><title>Pending:</title><p>the breakpoint is not set in your program.</p></item>
          <item><title>Permanent:</title><p>the breakpoint is set (its id number is displayed in parentheses).</p></item>
          <item><title>Temporary:</title><p>the breakpoint is set but will be deleted if reached.</p></item>
        </terms>
      </item>
    </terms>

    <note style="tip">
     <p>All breakpoints are kept across Anjuta sessions even if they correspond
     to a non-existing locations, for example in a source file of a shared library not
     loaded yet. In this case their states are set as pending.</p>
    </note>
  </section>

  <section>
    <title>Setting breakpoints</title>

    <steps>
      <item>
        <p>From the <gui>main menu</gui>, select <guiseq><gui>Debug</gui>
        <gui>Add Breakpoint...</gui></guiseq> or right click in the
        <gui>Breakpoint</gui> window and select <gui>Add Breakpoint...</gui>.
        </p>
      </item>
      <item>
        <p>Fill in the <gui>Location</gui>, which is the position of the
        breakpoint, and the other fields if desired.
        If a file is currently opened in the editor, the <gui>Location</gui>
        defaults to the current line.
        See <link xref="debug-breakpoint-dialog"/> for more information.</p>
      </item>
    </steps>

    <p>Another solution is to use the toggle breakpoint function. If there
    is no breakpoint on the current line, it will add one. Otherwise, it will
    remove it.</p>

    <steps>
      <item>
        <p>From the <gui>main menu</gui>, select <guiseq><gui>Debug</gui>
        <gui>Toggle Breakpoint</gui></guiseq> or right click in the
        <gui>Editor</gui> window and select <gui>Toggle Breakpoint</gui>.
        </p>
      </item>
    </steps>

  </section>


  <section>
    <title>Editing breakpoints</title>

    <p>You can't change the location of a breakpoint; create a new breakpoint
    instead. However, you can change the break condition or the pass count. To
    edit a breakpoint:</p>

    <steps>
      <item>
        <p>Select a breakpoint in the <gui>Breakpoint</gui> window.</p>
      </item>
      <item>
        <p>Right click in the <gui>Breakpoint</gui> window and select
        <gui>Edit Breakpoint...</gui>.
        </p>
      </item>
      <item>
        <p>Change the <gui>Condition</gui> or <gui>Pass Count</gui>
        fields and click on <gui>OK</gui> when you are done.
        See <link xref="debug-breakpoint-dialog"/> for more information.</p>
      </item>
    </steps>

  </section>


  <section>
    <title>Removing breakpoints</title>

	<p>You can remove a breakpoint using the toggle breakpoint function
	described above. However, if you want to remove more than one breakpoint
	or the breakpoint is in a different file than the one you are editing,
	you can use the breakpoint window:</p>

    <steps>
      <item>
        <p>Select a breakpoint in the <gui>Breakpoint</gui> window.</p>
      </item>
      <item>
        <p>Right click in the <gui>Breakpoint</gui> window and select
        <gui>Remove Breakpoint</gui>.
        </p>
      </item>
    </steps>

    <p>To remove all breakpoints:</p>

    <steps>
      <item>
        <p>From the <gui>main menu</gui>, select <guiseq><gui>Debug</gui>
        <gui>Remove All Breakpoints</gui></guiseq> or right-click in
        the <gui>Breakpoint</gui> window and select
        <gui>Remove All Breakpoints</gui>.</p>
      </item>
    </steps>

  </section>


  <section>
    <title>Enabling and disabling breakpoints</title>

    <p>Sometimes you might want to disable a breakpoint temporarily instead of
    deleting it altogether. To disable or re-enable a breakpoint:</p>

    <steps>
      <item>
        <p>Click on the <gui>Enable</gui> checkmark in the <gui>Breakpoint</gui>
        window or right click in the <gui>Breakpoint</gui> window and
        select <gui>Enable Breakpoint</gui> or <gui>Disable Breakpoint</gui>.</p>
      </item>
    </steps>

    <p>You can disable all breakpoints using:</p>

    <steps>
      <item>
        <p>From the <gui>main menu</gui>, select <guiseq><gui>Debug</gui>
        <gui>Disable All Breakpoints</gui></guiseq> or right-click in
        the <gui>Breakpoint</gui> window and select
        <gui>Disable All Breakpoints</gui>.</p>
      </item>
    </steps>

  </section>
  

</page>