[anjuta] manual: Document debugger plugin
- From: Sebastien Granjoux <sgranjoux src gnome org>
- To: commits-list gnome org
- Cc:
- Subject: [anjuta] manual: Document debugger plugin
- Date: Mon, 25 Jul 2011 19:55:11 +0000 (UTC)
commit b6428693e25ae6aafc1f13db819fb740138571dc
Author: SÃbastien Granjoux <seb sfo free fr>
Date: Mon Jul 25 18:24:55 2011 +0200
manual: Document debugger plugin
.../anjuta-manual/C/anjuta-debug-breakpoints.page | 26 ---
manuals/anjuta-manual/C/anjuta-debug-crash.page | 26 ---
manuals/anjuta-manual/C/anjuta-debug-start.page | 29 ---
manuals/anjuta-manual/C/autotools-build-build.page | 2 +-
.../anjuta-manual/C/debug-breakpoint-dialog.page | 53 ++++++
manuals/anjuta-manual/C/debug-breakpoint.page | 194 ++++++++++++++++++++
manuals/anjuta-manual/C/debug-cpu.page | 86 +++++++++
manuals/anjuta-manual/C/debug-custom.page | 42 +++++
.../{anjuta-debug-watches.page => debug-data.page} | 22 +--
...njuta-debug-watches.page => debug-execute.page} | 22 +--
manuals/anjuta-manual/C/debug-expression.page | 37 ++++
manuals/anjuta-manual/C/debug-information.page | 138 ++++++++++++++
manuals/anjuta-manual/C/debug-local.page | 71 +++++++
manuals/anjuta-manual/C/debug-process-dialog.page | 39 ++++
manuals/anjuta-manual/C/debug-run.page | 107 +++++++++++
manuals/anjuta-manual/C/debug-stack.page | 117 ++++++++++++
manuals/anjuta-manual/C/debug-step.page | 135 ++++++++++++++
manuals/anjuta-manual/C/debug-thread.page | 98 ++++++++++
manuals/anjuta-manual/C/debug-tips.page | 37 ++++
manuals/anjuta-manual/C/debug-watch.page | 149 +++++++++++++++
manuals/anjuta-manual/C/run-run.page | 2 +-
manuals/anjuta-manual/Makefile.am | 19 ++-
22 files changed, 1337 insertions(+), 114 deletions(-)
---
diff --git a/manuals/anjuta-manual/C/autotools-build-build.page b/manuals/anjuta-manual/C/autotools-build-build.page
index 3627aec..fa24a6a 100644
--- a/manuals/anjuta-manual/C/autotools-build-build.page
+++ b/manuals/anjuta-manual/C/autotools-build-build.page
@@ -43,7 +43,7 @@
<item>
<p>
From the <gui>main menu</gui>, select <guiseq><gui>Build</gui>
- <gui>Build Project</gui></guiseq> or press <key>Shift+F7</key>
+ <gui>Build Project</gui></guiseq> or press <keyseq><key>Shift</key><key>F7</key></keyseq>
to build the complete project, all subdirectories are built recursively.
</p>
</item>
diff --git a/manuals/anjuta-manual/C/debug-breakpoint-dialog.page b/manuals/anjuta-manual/C/debug-breakpoint-dialog.page
new file mode 100755
index 0000000..5cfe0ca
--- /dev/null
+++ b/manuals/anjuta-manual/C/debug-breakpoint-dialog.page
@@ -0,0 +1,53 @@
+<page xmlns="http://projectmallard.org/1.0/";
+ type="topic" style="task"
+ id="debug-breakpoint-dialog">
+
+ <info xmlns:facet="http://projectmallard.org/facet/1.0/";>
+ <facet:tag key="all-pages" value="whatever"/> <!--Include page in index-->
+ <facet:tag key="all-widgets" value="whatever"/> <!--Include page in index-->
+ <link type="seealso" xref="debug-breakpoint"/>
+ <revision pkgversion="3.0" version="0.1" date="2011-03-27" status="incomplete"/>
+ <desc>
+ Used to create or edit a breakpoint
+ </desc>
+ <credit type="author">
+ <name>SÃbastien Granjoux</name>
+ <email>seb sfo free fr</email>
+ </credit>
+ </info>
+
+ <title>Breakpoint Dialog</title>
+
+ <terms>
+ <item>
+ <title><gui>Location</gui></title>
+ <p>This is the position of the breakpoint. This cannot be changed on a
+ existing breakpoint. It can be specified using the following
+ formats:</p>
+ <list>
+ <item><p><var>file_name:line_number</var></p></item>
+ <item><p><var>function_name</var></p></item>
+ <item><p><var>file_name:function_name</var></p></item>
+ </list>
+ </item>
+ <item>
+ <title><gui>Condition</gui></title>
+ <p>It is an expression which should evaluate to a boolean value TRUE(1) or
+ FALSE(0).
+ Every time the breakpoint is encountered during your program's execution,
+ the break condition will be evaluated. The debugger will break the execution
+ only if the evaluation result is the TRUE value.</p>
+ <p>If you leave this field blank the condition is considered as always
+ TRUE.</p>
+ </item>
+ <item>
+ <title><gui>Pass Count</gui></title>
+ <p>This is an integer (unsigned) value which tells the debugger to
+ skip the breakpoint that number of times before it is considered. It
+ has a higher priority than the condition. Only when the count reaches
+ zero will the debugger evaluate the condition if it is present.</p>
+ </item>
+ </terms>
+
+</page>
+
diff --git a/manuals/anjuta-manual/C/debug-breakpoint.page b/manuals/anjuta-manual/C/debug-breakpoint.page
new file mode 100755
index 0000000..e2ef2b8
--- /dev/null
+++ b/manuals/anjuta-manual/C/debug-breakpoint.page
@@ -0,0 +1,194 @@
+<page xmlns="http://projectmallard.org/1.0/";
+ type="topic" style="task"
+ id="debug-breakpoint">
+
+ <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>
+ </info>
+
+ <title>Breakpoints</title>
+
+ <p>Breakpoints are used to stop the execution of the program at particular
+ points 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>
+ windows.</p>
+ </item>
+ </steps>
+
+ <p>This view has the following columns:</p>
+
+ <terms>
+ <item>
+ <title>Location</title>
+ <p>This is the position of the breakpoint in the source file. When
+ the breakpoint is set by the debugger, you can get additional
+ information such as the function containing the breakpoint.</p>
+ </item>
+ <item>
+ <title>Address</title>
+ <p>This field is filled with the address of the breakpoint
+ when it is set by the debugger.</p>
+ </item>
+ <item>
+ <title>Type</title>
+ <p>This always displays "breakpoint". It will be used in a
+ future release supporting different kinds of breakpoints.</p>
+ </item>
+ <item>
+ <title>Condition</title>
+ <p>This is the breakpoint condition. It is empty if no condition
+ is defined.</p>
+ </item>
+ <item>
+ <title>Pass count</title>
+ <p>When the debugger is not running, this column displays the
+ pass count of the breakpoint, or zero if it is not defined.</p>
+ <p>When the debugger is running, if the pass count is zero,
+ this column displays the number of times this breakpoint has
+ been triggered. If the pass count is not zero, both numbers
+ are displayed. The pass count is the second number.</p>
+ </item>
+ <item>
+ <title>State</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 given inside parenthesis).</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 by 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 at least the <gui>Location</gui> which is the position of the
+ breakpoint, if a file is currently opened in the editor it is
+ fill to put a breakpoint in the current line by default.
+ 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. Else 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>
+
+ <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> and <gui>Pass Count</gui>
+ field and click on <gui>OK</gui> to commit the changes.
+ See <link xref="debug-breakpoint-dialog"/> for more information.</p>
+ </item>
+ </steps>
+
+ </section>
+
+
+ <section>
+ <title>Removing breakpoints</title>
+
+ <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>You can remove all breakpoints using:</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 Breakpoint</gui>.</p>
+ </item>
+ </steps>
+
+ </section>
+
+
+ <section>
+ <title>Enabling and disabling breakpoints</title>
+
+ <steps>
+ <item>
+ <p>Click on the <gui>Enable</gui> column 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 Breakpoint</gui>.</p>
+ </item>
+ </steps>
+
+ </section>
+
+
+</page>
diff --git a/manuals/anjuta-manual/C/debug-cpu.page b/manuals/anjuta-manual/C/debug-cpu.page
new file mode 100755
index 0000000..624a1d8
--- /dev/null
+++ b/manuals/anjuta-manual/C/debug-cpu.page
@@ -0,0 +1,86 @@
+<page xmlns="http://projectmallard.org/1.0/";
+ type="topic" style="task"
+ id="debug-cpu">
+
+ <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-data" group="sixth"/>
+ <revision pkgversion="3.0" version="0.1" date="2011-03-27" status="incomplete"/>
+ <desc>
+ Examine CPU informations.
+ </desc>
+ <credit type="author">
+ <name>SÃbastien Granjoux</name>
+ <email>seb sfo free fr</email>
+ </credit>
+ </info>
+
+ <title>CPU</title>
+
+ <section>
+ <title>View CPU registers</title>
+
+ <steps>
+ <item>
+ <p>From the <gui>main menu</gui>, select <guiseq><gui>View</gui>
+ <gui>Registers</gui></guiseq> to open the <gui>Register</gui>
+ window.</p>
+ </item>
+ </steps>
+
+ <p>Register which value has changed since the last stop are in red. It is
+ possible ton change the value of any register by clicking in the value
+ column and entering a new value.</p>
+
+ </section>
+
+ <section>
+ <title>View memory</title>
+
+ <steps>
+ <item>
+ <p>From the <gui>main menu</gui>, select <guiseq><gui>View</gui>
+ <gui>Memory</gui></guiseq> to open the <gui>Memory</gui>
+ window.</p>
+ </item>
+ </steps>
+
+ <p>The first column displays memory addresses in hexadecimal, the second
+ displays memory contents in hexadecimal and the last column shows
+ memory contents in ASCII.</p>
+ <p>The addressing space of even a 32-bit microprocessor is very large
+ (4 gigabytes), so it is very difficult to go to a particular address
+ with the scrollbar. But you can click on the right mouse button and select
+ <gui>Goto address</gui> to get a small edit box where you can enter an
+ address in hexadecimal.</p>
+ </section>
+
+
+ <section>
+ <title>View Disassembly</title>
+
+
+ <steps>
+ <item>
+ <p>From the <gui>main menu</gui>, select <guiseq><gui>View</gui>
+ <gui>Memory</gui></guiseq> to open the <gui>Memory</gui>
+ window.</p>
+ </item>
+ </steps>
+
+ <p>The first column displays addresses in hexadecimal. In the second column,
+ you can have a label starting at the beginning of the line and ending with
+ a colon or a assembly-language instruction indented by 4 space characters.</p>
+
+ <p>The position in the disassembly window will be changed to the program
+ counter value when the program is stopped.</p>
+
+ <p>The addressing space of even a 32-bit microprocessor is very large
+ (4 gigabytes), so it is very difficult to go to a particular address
+ with the scrollbar. But you can click on the right mouse button and select
+ <gui>Goto address</gui> to get a small edit box where you can enter an
+ address in hexadecimal.</p>
+ </section>
+
+
+</page>
diff --git a/manuals/anjuta-manual/C/debug-custom.page b/manuals/anjuta-manual/C/debug-custom.page
new file mode 100755
index 0000000..d18f4fe
--- /dev/null
+++ b/manuals/anjuta-manual/C/debug-custom.page
@@ -0,0 +1,42 @@
+<page xmlns="http://projectmallard.org/1.0/";
+ type="topic" style="task"
+ id="debug-custom">
+
+ <info xmlns:facet="http://projectmallard.org/facet/1.0/";>
+ <facet:tag key="all-pages" value="whatever"/> <!--Include page in index-->
+ <link type="guide" xref="index#anjuta-debug" group="sixth"/>
+ <revision pkgversion="3.0" version="0.1" date="2011-03-27" status="incomplete"/>
+ <desc>
+ Use custom debugger command.
+ </desc>
+ <credit type="author">
+ <name>SÃbastien Granjoux</name>
+ <email>seb sfo free fr</email>
+ </credit>
+ </info>
+
+ <title>Custom command</title>
+
+ <p>Custom command can be send to the debugger using:</p>
+
+ <steps>
+ <item>
+ <p>From the <gui>main menu</gui>, select <guiseq><gui>Debug</gui>
+ <gui>Debugger Command</gui></guiseq>.</p>
+ </item>
+ <item>
+ <p>Enter your command.</p>
+ </item>
+ </steps>
+
+ <p>The output of the command is displayed in the message window used by
+ the debugger.</p>
+
+ <note style="warning">
+ <p>The command is sent directly to the debugger without performing any checks.
+ By example if you set a breakpoint like this, it will not appear in the
+ <gui>Breakpoint</gui> window. It is better to avoid using this
+ command unless you know exactly what you are doing.</p>
+ </note>
+
+</page>
diff --git a/manuals/anjuta-manual/C/anjuta-debug-watches.page b/manuals/anjuta-manual/C/debug-data.page
old mode 100644
new mode 100755
similarity index 57%
copy from manuals/anjuta-manual/C/anjuta-debug-watches.page
copy to manuals/anjuta-manual/C/debug-data.page
index a252680..7d1f57e
--- a/manuals/anjuta-manual/C/anjuta-debug-watches.page
+++ b/manuals/anjuta-manual/C/debug-data.page
@@ -1,26 +1,20 @@
<page xmlns="http://projectmallard.org/1.0/";
- type="topic" style="task"
- id="anjuta-debug-watches">
+ type="guide" style="2column"
+ id="debug-data" groups="first second third fourth fifth sixth seventh eighth">
<info xmlns:facet="http://projectmallard.org/facet/1.0/";>
<facet:tag key="all-pages" value="whatever"/> <!--Include page in index-->
<link type="guide" xref="index#anjuta-debug" group="fourth"/>
<revision pkgversion="3.0" version="0.1" date="2011-03-27" status="incomplete"/>
+ <desc>
+ Examine program Data.
+ </desc>
<credit type="author">
- <name>Johannes Schmid</name>
- <email>jhs gnome org</email>
+ <name>SÃbastien Granjoux</name>
+ <email>seb sfo free fr</email>
</credit>
</info>
- <title>Watch the value of variables</title>
-
-<section>
-<title>Local variables</title>
-
-</section>
-
-<section>
-<title>Add variables watches</title>
-</section>
+ <title>Examine data</title>
</page>
diff --git a/manuals/anjuta-manual/C/anjuta-debug-watches.page b/manuals/anjuta-manual/C/debug-execute.page
old mode 100644
new mode 100755
similarity index 57%
rename from manuals/anjuta-manual/C/anjuta-debug-watches.page
rename to manuals/anjuta-manual/C/debug-execute.page
index a252680..7ea51de
--- a/manuals/anjuta-manual/C/anjuta-debug-watches.page
+++ b/manuals/anjuta-manual/C/debug-execute.page
@@ -1,26 +1,20 @@
<page xmlns="http://projectmallard.org/1.0/";
- type="topic" style="task"
- id="anjuta-debug-watches">
+ type="guide" style="2column"
+ id="debug-execute" groups="first second third fourth fifth sixth seventh">
<info xmlns:facet="http://projectmallard.org/facet/1.0/";>
<facet:tag key="all-pages" value="whatever"/> <!--Include page in index-->
<link type="guide" xref="index#anjuta-debug" group="fourth"/>
<revision pkgversion="3.0" version="0.1" date="2011-03-27" status="incomplete"/>
+ <desc>
+ Control program execution.
+ </desc>
<credit type="author">
- <name>Johannes Schmid</name>
- <email>jhs gnome org</email>
+ <name>SÃbastien Granjoux</name>
+ <email>seb sfo free fr</email>
</credit>
</info>
- <title>Watch the value of variables</title>
-
-<section>
-<title>Local variables</title>
-
-</section>
-
-<section>
-<title>Add variables watches</title>
-</section>
+ <title>Control execution</title>
</page>
diff --git a/manuals/anjuta-manual/C/debug-expression.page b/manuals/anjuta-manual/C/debug-expression.page
new file mode 100755
index 0000000..50f792e
--- /dev/null
+++ b/manuals/anjuta-manual/C/debug-expression.page
@@ -0,0 +1,37 @@
+<page xmlns="http://projectmallard.org/1.0/";
+ type="topic" style="task"
+ id="debug-expression">
+
+ <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-data" group="first"/>
+ <revision pkgversion="3.0" version="0.1" date="2011-03-27" status="incomplete"/>
+ <desc>
+ Evaluate expressions and modify variables.
+ </desc>
+ <credit type="author">
+ <name>SÃbastien Granjoux</name>
+ <email>seb sfo free fr</email>
+ </credit>
+ </info>
+
+ <title>Examine expressions</title>
+
+ <section>
+ <title>Inspect an expression and modify a variable</title>
+
+ <steps>
+ <item>
+ <p>From the <gui>main menu</gui>, select <guiseq><gui>Debug</gui>
+ <gui>Inspect/Evaluate</gui></guiseq> or right click in the
+ <gui>Editor</gui> window and select <gui>Inspect/Evaluate</gui>.</p>
+ </item>
+ <item>
+ <p>If the expression is a variable name, you can change its value
+ by clicking on the <gui>Value</gui> column and enter a new value.</p>
+ </item>
+ </steps>
+
+ </section>
+
+</page>
diff --git a/manuals/anjuta-manual/C/debug-information.page b/manuals/anjuta-manual/C/debug-information.page
new file mode 100755
index 0000000..138781f
--- /dev/null
+++ b/manuals/anjuta-manual/C/debug-information.page
@@ -0,0 +1,138 @@
+<page xmlns="http://projectmallard.org/1.0/";
+ type="topic" style="task"
+ id="debug-information">
+
+ <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-data" group="seventh"/>
+ <revision pkgversion="3.0" version="0.1" date="2011-03-27" status="incomplete"/>
+ <desc>
+ Examine additional program informations.
+ </desc>
+ <credit type="author">
+ <name>SÃbastien Granjoux</name>
+ <email>seb sfo free fr</email>
+ </credit>
+ </info>
+
+ <title>Miscellaneous informations</title>
+
+ <section>
+ <title>View shared libraries</title>
+
+ <steps>
+ <item>
+ <p>From the <gui>main menu</gui>, select <guiseq><gui>Debug</gui>
+ <gui>Info</gui><gui>Shared Libraries</gui></guiseq>.</p>
+ </item>
+ </steps>
+
+ <p>This open a window which will list all shared libraries the program has loaded
+ and their locations in memory. It also shows whether each library's symbol table is
+ loaded or not (Yes/No).</p>
+ </section>
+
+
+ <section>
+ <title>View signals</title>
+
+ <steps>
+ <item>
+ <p>From the <gui>main menu</gui>, select <guiseq><gui>Debug</gui>
+ <gui>Info</gui><gui>Kernels signals</gui></guiseq>.</p>
+ </item>
+ </steps>
+
+ <p>This list all available signals with a small description and three
+ columns to specify what to do when a signal is received:</p>
+
+ <terms>
+ <item>
+ <title>Stop</title>
+ <p>The debugger stops the program execution when the program receives
+ this signal.</p>
+ </item>
+ <item>
+ <title>Print</title>
+ <p>The debugger display the received signal.</p>
+ </item>
+ <item>
+ <title>Pass</title>
+ <p>The debugger pass the signal to the program.</p>
+ </item>
+ </terms>
+
+ <note style="bug">
+ <p>The context menu that is displayed when you click on the right mouse
+ button has all its items disabled because the corresponding functions
+ are not implemented yet.</p>
+ </note>
+
+ </section>
+
+
+ <section>
+ <title>Information about used files</title>
+
+ <steps>
+ <item>
+ <p>From the <gui>main menu</gui>, select <guiseq><gui>Debug</gui>
+ <gui>Info</gui><gui>Info Target files</gui></guiseq>.</p>
+ </item>
+ </steps>
+
+ </section>
+
+ <section>
+ <title>Information about program</title>
+ <steps>
+ <item>
+ <p>From the <gui>main menu</gui>, select <guiseq><gui>Debug</gui>
+ <gui>Info</gui><gui>Info Program</gui></guiseq>.</p>
+ </item>
+ </steps>
+
+ </section>
+
+ <section>
+ <title>Information about kernel structure</title>
+ <steps>
+ <item>
+ <p>From the <gui>main menu</gui>, select <guiseq><gui>Debug</gui>
+ <gui>Info</gui><gui>Kernel user struct</gui></guiseq>.</p>
+ </item>
+ </steps>
+ </section>
+
+ <section>
+ <title>Information about global variables</title>
+ <steps>
+ <item>
+ <p>From the <gui>main menu</gui>, select <guiseq><gui>Debug</gui>
+ <gui>Info</gui><gui>Info Global Variable</gui></guiseq>.</p>
+ </item>
+ </steps>
+ </section>
+
+ <section>
+ <title>Information about the current frame</title>
+ <steps>
+ <item>
+ <p>From the <gui>main menu</gui>, select <guiseq><gui>Debug</gui>
+ <gui>Info</gui><gui>Info Current Frame</gui></guiseq>.</p>
+ </item>
+ </steps>
+ </section>
+
+ <section>
+ <title>Information about the current function arguments</title>
+ <steps>
+ <item>
+ <p>From the <gui>main menu</gui>, select <guiseq><gui>Debug</gui>
+ <gui>Info</gui><gui>Info Arguments</gui></guiseq>.</p>
+ </item>
+ </steps>
+ </section>
+
+
+</page>
diff --git a/manuals/anjuta-manual/C/debug-local.page b/manuals/anjuta-manual/C/debug-local.page
new file mode 100755
index 0000000..7322b1a
--- /dev/null
+++ b/manuals/anjuta-manual/C/debug-local.page
@@ -0,0 +1,71 @@
+<page xmlns="http://projectmallard.org/1.0/";
+ type="topic" style="task"
+ id="debug-local">
+
+ <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-data" group="third"/>
+ <revision pkgversion="3.0" version="0.1" date="2011-03-27" status="incomplete"/>
+ <desc>
+ Examine local variables.
+ </desc>
+ <credit type="author">
+ <name>SÃbastien Granjoux</name>
+ <email>seb sfo free fr</email>
+ </credit>
+ </info>
+
+ <title>Local variables</title>
+
+ <p>Local variables of the current frame (the current function in which the
+ program control is present) are displayed in the <gui>Locals</gui> window.
+ During execution of the program (e.g. during single stepping), local
+ variables will be updated. If any variable value was changed in the last debugging step, its
+ value will be highlighted in red. Variables are presented in a tree form for easy
+ view.</p>
+
+ <section>
+ <title>Listing local variables</title>
+
+ <steps>
+ <item>
+ <p>From the <gui>main menu</gui>, select <guiseq><gui>View</gui>
+ <gui>Locals</gui></guiseq> to open the <gui>Local</gui>
+ window.</p>
+ </item>
+ </steps>
+
+ <p>All local variables are displayed in a tree view with children used to
+ represent structure or array members.</p>
+
+ <terms>
+ <item>
+ <title>Variable</title>
+ <p>The name of the variable.</p>
+ </item>
+ <item>
+ <title>Value</title>
+ <p>The variable value</p>
+ </item>
+ <item>
+ <title>Type</title>
+ <p>The type of the variable</p>
+ </item>
+ </terms>
+ </section>
+
+ <section>
+ <title>Changing the value of a variable</title>
+
+ <steps>
+ <item>
+ <p>In the <gui>Local</gui> window, select the variable you want to
+ edit and double click in the <gui>Value</gui> column.</p>
+ </item>
+ <item>
+ <p>Type the new value</p>
+ </item>
+ </steps>
+ </section>
+
+</page>
diff --git a/manuals/anjuta-manual/C/debug-process-dialog.page b/manuals/anjuta-manual/C/debug-process-dialog.page
new file mode 100755
index 0000000..d705dcf
--- /dev/null
+++ b/manuals/anjuta-manual/C/debug-process-dialog.page
@@ -0,0 +1,39 @@
+<page xmlns="http://projectmallard.org/1.0/";
+ type="topic" style="task"
+ id="debug-process-dialog">
+
+ <info xmlns:facet="http://projectmallard.org/facet/1.0/";>
+ <facet:tag key="all-pages" value="whatever"/> <!--Include page in index-->
+ <facet:tag key="all-widgets" value="whatever"/> <!--Include page in index-->
+ <revision pkgversion="3.0" version="0.1" date="2011-03-27" status="incomplete"/>
+ <desc>
+ Attach to process dialog
+ </desc>
+ <credit type="author">
+ <name>SÃbastien Granjoux</name>
+ <email>seb sfo free fr</email>
+ </credit>
+ </info>
+
+ <title>Attach to process Dialog</title>
+
+ <p>The <gui>process</gui> dialog allows you to select a currently running process</p>
+
+ <terms>
+ <item>
+ <title><gui>Hide paths</gui></title>
+ <p>This hides command pathes in the process list if checked.</p>
+ </item>
+ <item>
+ <title><gui>Hide process parameters</gui></title>
+ <p>This hides the command line arguments in the process list if checked.</p>
+ </item>
+ <item>
+ <title><gui>Display process tree</gui></title>
+ <p>If unchecked, the processes are displayed in a list. If checked the
+ processes are displayed in a tree.</p>
+ </item>
+ </terms>
+
+</page>
+
diff --git a/manuals/anjuta-manual/C/debug-run.page b/manuals/anjuta-manual/C/debug-run.page
new file mode 100755
index 0000000..cdc985f
--- /dev/null
+++ b/manuals/anjuta-manual/C/debug-run.page
@@ -0,0 +1,107 @@
+<page xmlns="http://projectmallard.org/1.0/";
+ type="topic" style="task"
+ id="debug-run">
+
+ <info xmlns:facet="http://projectmallard.org/facet/1.0/";>
+ <facet:tag key="all-pages" value="whatever"/> <!--Include page in index-->
+ <link type="guide" xref="index#anjuta-debug" group="second"/>
+ <link type="seealso" xref="run-parameters-dialog"/>
+ <link type="seealso" xref="autotools-build-configure"/>
+ <revision pkgversion="3.0" version="0.1" date="2011-03-27" status="incomplete"/>
+ <desc>
+ Start a program with the debugger.
+ </desc>
+ <credit type="author">
+ <name>SÃbastien Granjoux</name>
+ <email>seb sfo free fr</email>
+ </credit>
+ </info>
+
+ <title>Debug a program</title>
+
+ <section>
+ <title>Start a program in the debugger</title>
+
+ <p>The current program is defined in the <gui>run parameter</gui> dialog.
+ See <link xref="run-parameters-dialog"/> for more information. This
+ program can be started in the debugger using:</p>
+
+ <steps>
+ <item>
+ <p>From the <gui>main menu</gui>, select <guiseq><gui>Run</gui>
+ <gui>Debug Program</gui></guiseq> or press <keyseq><key>Shift</key><key>F12</key></keyseq></p>
+ </item>
+ </steps>
+
+ <note style="tip">
+ <p>A program can be more difficult to debug if it is highly optimized
+ or if debugging information are missing. This is defined in the
+ configure step. Normally, a Debug configuration with no optimization
+ and all debugging informations is defined. Anjuta display a warning
+ if this configuration is not used.
+ See <link xref="autotools-build-configure"/> for more information.</p>
+ </note>
+ </section>
+
+ <section>
+ <title>Debug an already running application</title>
+
+ <p>The debugger could be used on an already running application.</p>
+
+ <steps>
+ <item>
+ <p>From the <gui>main menu</gui>, select <guiseq><gui>Run</gui>
+ <gui>Debug Process...</gui></guiseq>
+ to get a dialog listing all currently running process.</p>
+ </item>
+ <item>
+ <p>Select a process in the <gui>attach to process</gui> dialog
+ and click on <gui>Attach</gui> to start the debugger on this
+ process. See <link xref="debug-process-dialog"/> for more details.</p>
+ </item>
+ </steps>
+ </section>
+
+ <section>
+ <title>Debug a remote application</title>
+
+ <p>The debugger can be used to debug an application running on another
+ computer connected through a TCP or a serial connection.</p>
+
+ <steps>
+ <item>
+ <p>From the <gui>main menu</gui>, select <guiseq><gui>Run</gui>
+ <gui>Debug Remote...</gui></guiseq></p>
+ </item>
+ <item>
+ <p>Select the type of the connection with the remote application,
+ <gui>Serial Line</gui> or <gui>TCP/IP</gui>.</p>
+ </item>
+ <item>
+ <p>For a TCP connection, fill <gui>Address</gui> and <gui>Port</gui>
+ field</p>
+ <p>For a serial connection, fill the text box below with the serial
+ device name, by example <cmd>/dev/ttyb</cmd>.</p>
+ </item>
+ <item>
+ <p>Click on <gui>Connect</gui> to start the debugger and connect to
+ the remote target.</p>
+ </item>
+ </steps>
+
+ </section>
+
+ <section>
+ <title>Stop the debugger</title>
+
+ <p>The debugger and the program can be stop at any time using:</p>
+
+ <steps>
+ <item>
+ <p>From the <gui>main menu</gui>, select <guiseq><gui>Run</gui>
+ <gui>Stop Debugger</gui></guiseq>.</p>
+ </item>
+ </steps>
+
+ </section>
+</page>
diff --git a/manuals/anjuta-manual/C/debug-stack.page b/manuals/anjuta-manual/C/debug-stack.page
new file mode 100755
index 0000000..4510fe6
--- /dev/null
+++ b/manuals/anjuta-manual/C/debug-stack.page
@@ -0,0 +1,117 @@
+<page xmlns="http://projectmallard.org/1.0/";
+ type="topic" style="task"
+ id="debug-stack">
+
+ <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-data" group="fourth"/>
+ <revision pkgversion="3.0" version="0.1" date="2011-03-27" status="incomplete"/>
+ <desc>
+ Examine stack.
+ </desc>
+ <credit type="author">
+ <name>SÃbastien Granjoux</name>
+ <email>seb sfo free fr</email>
+ </credit>
+ </info>
+
+ <title>Stack</title>
+
+ <section>
+ <title>List stack frames</title>
+
+ <p>A stack frame is the area of the stack associated to each function call.
+ It lists all functions and their arguments in the sequence they were called.
+ Each stack frame is numbered starting from 0 for the current function.</p>
+
+ <steps>
+ <item>
+ <p>From the <gui>main menu</gui>, select <guiseq><gui>View</gui>
+ <gui>Stack</gui></guiseq> to open the <gui>Stack</gui>
+ window.</p>
+ </item>
+ </steps>
+
+ <p>Each stack frame contains the following information:</p>
+
+ <terms>
+ <item>
+ <title>Active</title>
+ <p>This contains a yellow arrow to represent the active stack frame, by
+ default it is the frame 0, the current function. All evaluations and
+ local variables are relative to this selected frame. You can change
+ the active stack frame to examine local variables in other functions.</p>
+ </item>
+ <item>
+ <title>Frame</title>
+ <p>This is the frame number stating from 0 for the current function.
+ The first function of your program, main for a C program by example,
+ has the highest number.</p>
+ </item>
+ <item>
+ <title>File</title>
+ <p>The name of the file containing the function corresponding to
+ this frame.</p>
+ </item>
+ <item>
+ <title>Line</title>
+ <p>The line number of the function corresponding to this frame.</p>
+ </item>
+ <item>
+ <title>Function</title>
+ <p>The name of the function corresponding to this frame.</p>
+ </item>
+ <item>
+ <title>Address</title>
+ <p>The address of the function corresponding to this frame.</p>
+ </item>
+ <item>
+ <title>Arguments</title>
+ <p>The function arguments.</p>
+ </item>
+ </terms>
+
+ </section>
+
+
+ <section>
+ <title>Change current stack frame</title>
+
+ <steps>
+ <item>
+ <p>In the <gui>Stack</gui> window, select the frame you want.</p>
+ </item>
+ <item>
+ <p>Right click and select <gui>Set current frame</gui></p>
+ </item>
+ </steps>
+ </section>
+
+
+ <section>
+ <title>View current function</title>
+
+ <steps>
+ <item>
+ <p>In the <gui>Stack</gui> window, select the frame you want.</p>
+ </item>
+ <item>
+ <p>Double click or right click and select <gui>View Source</gui></p>
+ </item>
+ </steps>
+ </section>
+
+
+ <section>
+ <title>Get a stack trace</title>
+
+ <steps>
+ <item>
+ <p>In the <gui>Stack</gui> window right click and select
+ <gui>Get stack trace</gui></p>
+ </item>
+ </steps>
+ </section>
+
+
+</page>
diff --git a/manuals/anjuta-manual/C/debug-step.page b/manuals/anjuta-manual/C/debug-step.page
new file mode 100755
index 0000000..7cad9b4
--- /dev/null
+++ b/manuals/anjuta-manual/C/debug-step.page
@@ -0,0 +1,135 @@
+<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>
+ </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. You cannot go
+ backward yet though. This is essential for tracking program behavior.</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></p> or
+ click on the <gui>Step In</gui> icon in the toolbar.
+ </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 step in 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 this instruction is a call to a subroutine, in this 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></p> or
+ click on the <gui>Step Out</gui> icon in the toolbar.
+ </item>
+ </steps>
+
+ <p>It 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></p> or
+ click on the <gui>Continue</gui> icon in the toolbar.
+ </item>
+ </steps>
+
+ <p>This command restarts the program 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></p> or
+ click on the <gui>Run to</gui> icon in the toolbar.
+ </item>
+ </steps>
+
+ <p>This restarts the program until the line or the
+ address (if the <gui>Disassembly window</gui> has the focus) at
+ the cursor is reached.</p>
+ </section>
+
+ <section>
+ <title>Stop 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 return control to the debugger allowing
+ perform all debugging tasks, like inspecting data, adding breakpoints...</p>
+ </section>
+
+
+</page>
diff --git a/manuals/anjuta-manual/C/debug-thread.page b/manuals/anjuta-manual/C/debug-thread.page
new file mode 100755
index 0000000..9c430fa
--- /dev/null
+++ b/manuals/anjuta-manual/C/debug-thread.page
@@ -0,0 +1,98 @@
+<page xmlns="http://projectmallard.org/1.0/";
+ type="topic" style="task"
+ id="debug-thread">
+
+ <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-data" group="fifth"/>
+ <revision pkgversion="3.0" version="0.1" date="2011-03-27" status="incomplete"/>
+ <desc>
+ Examine threads.
+ </desc>
+ <credit type="author">
+ <name>SÃbastien Granjoux</name>
+ <email>seb sfo free fr</email>
+ </credit>
+ </info>
+
+ <title>Threads</title>
+
+ <section>
+ <title>List threads</title>
+
+ <p>A program can be composed of several threads. All these threads are
+ executed independently having their own registers, stack and local
+ variables but sharing global variables.</p>
+
+ <steps>
+ <item>
+ <p>From the <gui>main menu</gui>, select <guiseq><gui>View</gui>
+ <gui>Thread</gui></guiseq> to open the <gui>Thread</gui>
+ window.</p>
+ </item>
+ </steps>
+
+ <p>Each thread contains the following information:</p>
+
+ <terms>
+ <item>
+ <title>Active</title>
+ <p>This contains a yellow arrow to represent the active thread.</p>
+ </item>
+ <item>
+ <title>ID</title>
+ <p>This is a number corresponding to each thread.</p>
+ </item>
+ <item>
+ <title>File</title>
+ <p>The name of the file containing the function corresponding to
+ the current frame of the current thread.</p>
+ </item>
+ <item>
+ <title>Line</title>
+ <p>The line number of the function corresponding to the current
+ frame of the current thread.</p>
+ </item>
+ <item>
+ <title>Function</title>
+ <p>The name of the function corresponding to the frame of the
+ current thread.</p>
+ </item>
+ <item>
+ <title>Address</title>
+ <p>The address of the function corresponding to the frame of the
+ current thread.</p>
+ </item>
+ </terms>
+
+ </section>
+
+ <section>
+ <title>Change current thread</title>
+
+ <steps>
+ <item>
+ <p>In the <gui>Thread</gui> window, select the thread you want.</p>
+ </item>
+ <item>
+ <p>Right click and select <gui>Set current thread</gui></p>
+ </item>
+ </steps>
+ </section>
+
+
+ <section>
+ <title>View current function</title>
+
+ <steps>
+ <item>
+ <p>In the <gui>Thread</gui> window, select the thread you want.</p>
+ </item>
+ <item>
+ <p>Double click or right click and select <gui>View Source</gui></p>
+ </item>
+ </steps>
+ </section>
+
+
+</page>
diff --git a/manuals/anjuta-manual/C/debug-tips.page b/manuals/anjuta-manual/C/debug-tips.page
new file mode 100755
index 0000000..1ed1ac8
--- /dev/null
+++ b/manuals/anjuta-manual/C/debug-tips.page
@@ -0,0 +1,37 @@
+<page xmlns="http://projectmallard.org/1.0/";
+ type="topic" style="task"
+ id="debug-tips">
+
+ <info xmlns:facet="http://projectmallard.org/facet/1.0/";>
+ <facet:tag key="all-pages" value="whatever"/> <!--Include page in index-->
+ <link type="guide" xref="index#anjuta-debug" group="fifth"/>
+ <revision pkgversion="3.0" version="0.1" date="2011-03-27" status="incomplete"/>
+ <desc>
+ Debugging tips and tricks.
+ </desc>
+ <credit type="author">
+ <name>SÃbastien Granjoux</name>
+ <email>seb sfo free fr</email>
+ </credit>
+ </info>
+
+ <title>Debug tips</title>
+
+ <section>
+ <title>Fix Glib/Gtk+ critical errors</title>
+
+ <p>A program can be stopped as soon as it gets a GLib critical errors if
+ the environment variable <sys>G_DEBUG</sys> has the value
+ <sys>fatal_criticals</sys>. This environment variable can be set in the
+ <link xref="run-parameters-dialog"/>.</p>
+ <p>Then you need to run the program with the debugger and use it until
+ you get the critical error. At that time, the debugger will stop your
+ program and you have to look at the
+ <link xref="debug-stack"/> to check where this error comes from.</p>
+ <p>The top function with frame number 0 is in GLib, so you have to look
+ down in the stack, typically the error comes from the first function in your
+ program.</p>
+
+ </section>
+
+</page>
diff --git a/manuals/anjuta-manual/C/debug-watch.page b/manuals/anjuta-manual/C/debug-watch.page
new file mode 100755
index 0000000..182a0ee
--- /dev/null
+++ b/manuals/anjuta-manual/C/debug-watch.page
@@ -0,0 +1,149 @@
+<page xmlns="http://projectmallard.org/1.0/";
+ type="topic" style="task"
+ id="debug-watch">
+
+ <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-data" group="second"/>
+ <revision pkgversion="3.0" version="0.1" date="2011-03-27" status="incomplete"/>
+ <desc>
+ Monitor expressions and variables.
+ </desc>
+ <credit type="author">
+ <name>SÃbastien Granjoux</name>
+ <email>seb sfo free fr</email>
+ </credit>
+ </info>
+
+ <title>Watch expression</title>
+
+ <section>
+ <title>List watched expressions</title>
+
+ <steps>
+ <item>
+ <p>From the <gui>main menu</gui>, select <guiseq><gui>View</gui>
+ <gui>Watches</gui></guiseq> to open the <gui>Watches</gui>
+ window.</p>
+ </item>
+ </steps>
+
+ <p>Like local variables, all watches expression are displayed in a tree view with children used to
+ represent structure or array members.</p>
+
+ <terms>
+ <item>
+ <title>Variable</title>
+ <p>The name of the variable or the expression.</p>
+ </item>
+ <item>
+ <title>Value</title>
+ <p>The variable or expression value.</p>
+ </item>
+ <item>
+ <title>Type</title>
+ <p>The type of the variable or of the expression result.</p>
+ </item>
+ </terms>
+ </section>
+
+ <section>
+ <title>Update watches</title>
+
+ <p>Watch expressions can be updated automatically as soon as the
+ program is stopped or on user request.</p>
+
+ <steps>
+ <item>
+ <p>In the <gui>Watches</gui> windows select the watch you want to
+ update automatically, right click and check that <gui>Automatic Update</gui>
+ if checked, if not select it.</p>
+ </item>
+ </steps>
+
+ <steps>
+ <item>
+ <p>In the <gui>Watches</gui> window, right click and select <gui>Update Watch</gui> to
+ update the selected watch.</p>
+ </item>
+ </steps>
+
+ <steps>
+ <item>
+ <p>In the <gui>Watches</gui> window, right click and select <gui>Update all</gui> to
+ update all watches at the same time.</p>
+ </item>
+ </steps>
+
+ </section>
+
+
+ <section>
+ <title>Add a watch on an expression</title>
+
+ <steps>
+ <item>
+ <p>From the <gui>main menu</gui>, select <guiseq><gui>Debug</gui>
+ <gui>Add Watch...</gui></guiseq> or in the <gui>Watches</gui>
+ windows right click and select <gui>Add Watch...</gui>.</p>
+ </item>
+ <item>
+ <p>Enter the expression to watch. Check <gui>Automatic Update</gui>
+ if you want that the expression is evaluated each time the program
+ is stopped.</p>
+ </item>
+ </steps>
+
+ <p>An expression can be evaluate and then added as a watch using:</p>
+
+ <steps>
+ <item>
+ <p>From the <gui>main menu</gui>, select <guiseq><gui>Debug</gui>
+ <gui>Inspect/Evaluate</gui></guiseq> or right click in the
+ <gui>Editor</gui> window and select <gui>Inspect/Evaluate</gui>.</p>
+ </item>
+ <item>
+ <p>Click on <gui>Add</gui> button to add this expression in the watches
+ list.</p>
+ </item>
+ </steps>
+
+ </section>
+
+ <section>
+ <title>Remove a watch</title>
+
+ <steps>
+ <item>
+ <p>In the <gui>Watches</gui> windows select the watch you want to remove
+ then right click and select <gui>Remove Watch</gui>.</p>
+ </item>
+ </steps>
+
+ <p>All watches can be removed at the same time.</p>
+
+ <steps>
+ <item>
+ <p>In the <gui>Watches</gui> right click and select <gui>Remove all</gui>.</p>
+ </item>
+ </steps>
+
+ </section>
+
+ <section>
+ <title>Changing the value of a variable</title>
+
+ <steps>
+ <item>
+ <p>If a watch expression corresponds to a variable you can change
+ its value. In the <gui>Watches</gui> window, select the variable you want to
+ edit and double click in the <gui>Value</gui> column.</p>
+ </item>
+ <item>
+ <p>Enter the new value.</p>
+ </item>
+ </steps>
+ </section>
+
+
+</page>
diff --git a/manuals/anjuta-manual/C/run-run.page b/manuals/anjuta-manual/C/run-run.page
index 97de488..a2a864a 100644
--- a/manuals/anjuta-manual/C/run-run.page
+++ b/manuals/anjuta-manual/C/run-run.page
@@ -9,7 +9,7 @@
<link type="seealso" xref="autotools-build-install"/>
<revision pkgversion="3.0" version="0.1" date="2011-03-27" status="incomplete"/>
<desc>
- Run a program without the debugger.
+ Start a program without the debugger.
</desc>
<credit type="author">
<name>SÃbastien Granjoux</name>
diff --git a/manuals/anjuta-manual/Makefile.am b/manuals/anjuta-manual/Makefile.am
index bd6a4ea..e10dbf8 100644
--- a/manuals/anjuta-manual/Makefile.am
+++ b/manuals/anjuta-manual/Makefile.am
@@ -7,11 +7,24 @@ DOC_PAGES = anjuta-code-assist.page \
anjuta-code-help.page \
anjuta-code-indentation.page \
anjuta-code-symbols.page \
- anjuta-debug-breakpoints.page \
- anjuta-debug-crash.page \
- anjuta-debug-watches.page \
anjuta-glade-signals.page \
anjuta-glade-start.page \
+ debug-breakpoint-dialog.page \
+ debug-breakpoint.page \
+ debug-cpu.page \
+ debug-custom.page \
+ debug-data.page \
+ debug-execute.page \
+ debug-expression.page \
+ debug-information.page \
+ debug-local.page \
+ debug-process-dialog.page \
+ debug-run.page \
+ debug-stack.page \
+ debug-step.page \
+ debug-thread.page \
+ debug-tips.page \
+ debug-watch.page \
run-run.page \
run-parameters-dialog.page \
autotools-build-build.page \
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]
