nemiver r746 - in trunk: . help/C
- From: jjongsma svn gnome org
- To: svn-commits-list gnome org
- Subject: nemiver r746 - in trunk: . help/C
- Date: Sun, 10 Feb 2008 17:33:19 +0000 (GMT)
Author: jjongsma
Date: Sun Feb 10 17:33:19 2008
New Revision: 746
URL: http://svn.gnome.org/viewvc/nemiver?rev=746&view=rev
Log:
More minor manual updates
Modified:
trunk/ChangeLog
trunk/help/C/nemiver.xml
Modified: trunk/help/C/nemiver.xml
==============================================================================
--- trunk/help/C/nemiver.xml (original)
+++ trunk/help/C/nemiver.xml Sun Feb 10 17:33:19 2008
@@ -1,6 +1,5 @@
<?xml version="1.0"?>
-<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN"
-"http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd"; [
+<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN" "http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd"; [
<!ENTITY appversion "0.5.0">
<!ENTITY manrevision "2.0">
<!ENTITY date "February 2008">
@@ -25,8 +24,8 @@
<title>&app; Manual</title>
<copyright>
<year>2008</year>
- <holder>Jonathon Jongsma</holder> </copyright>
-
+ <holder>Jonathon Jongsma</holder>
+ </copyright>
<!-- translators: uncomment this:
<copyright>
@@ -38,9 +37,7 @@
<publisher role="maintainer">
<publishername>&app; Project</publishername>
</publisher>
-
- <xi:include href="legal.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
-
+ <xi:include xmlns:xi="http://www.w3.org/2001/XInclude"; href="legal.xml"/>
<authorgroup>
<author>
<firstname>Jonathon</firstname>
@@ -49,7 +46,6 @@
<orgname>GNOME</orgname>
</affiliation>
</author>
-
<!-- This is appropriate place for other contributors: translators,
maintainers, etc. Commented out by default.
<othercredit role="translator">
@@ -63,7 +59,6 @@
</othercredit>
-->
</authorgroup>
-
<!-- According to GNU FDL, revision history is mandatory if you are -->
<!-- modifying/reusing someone else's document. If not, you can omit it. -->
<revhistory>
@@ -101,10 +96,15 @@
</para>
</abstract>
</articleinfo>
- <indexterm><primary>&app;</primary></indexterm>
- <indexterm><primary>debugger</primary></indexterm>
- <indexterm><primary>gdb</primary></indexterm>
-
+ <indexterm>
+ <primary>&app;</primary>
+ </indexterm>
+ <indexterm>
+ <primary>debugger</primary>
+ </indexterm>
+ <indexterm>
+ <primary>gdb</primary>
+ </indexterm>
<!-- ============= Document Body ============================= -->
<!-- ============= Introduction ============================== -->
<sect1 id="nemiver-sect-intro">
@@ -118,13 +118,15 @@
<sect2 id="nemiver-sect-perspectives">
<title>Perspectives</title>
<para>
- &app; is built with a plugin system that can offer several different
- perspectives. Currently the only perspective provided is a debugging
- perspective, but in the future, there may be perspectives added for
- valgrind, or for profiling tools such as oprofile.
+ &app; is designed as a generic graphical
+ <interface>workbench</interface> and a plugin system that can offer
+ several different perspectives. Currently the only perspective
+ provided is a debugging perspective, but in the future, there may be
+ perspectives added for memory debugging with
+ <application>valgrind</application>, or for profiling tools such as
+ <application>oprofile</application>.
</para>
</sect2>
-
</sect1>
<sect1 id="nemiver-sect-getting-started">
<title>Getting Started</title>
@@ -142,8 +144,7 @@
<term><guimenu>Applications</guimenu> menu</term>
<listitem>
<para>
- Choose <menuchoice> <guisubmenu>Programming</guisubmenu>
- <guimenuitem>Nemiver Debugger</guimenuitem> </menuchoice>.
+ Choose <menuchoice><guisubmenu>Programming</guisubmenu><guimenuitem>Nemiver Debugger</guimenuitem></menuchoice>.
</para>
</listitem>
</varlistentry>
@@ -178,7 +179,8 @@
<imageobject>
<imagedata fileref="figures/main-window.png" format="PNG"/>
</imageobject>
- <textobject> <phrase>Shows &app; main window.</phrase>
+ <textobject>
+ <phrase>Shows &app; main window.</phrase>
</textobject>
</mediaobject>
</screenshot>
@@ -188,7 +190,8 @@
elements:
</para>
<variablelist>
- <varlistentry> <term>Menubar</term>
+ <varlistentry>
+ <term>Menubar</term>
<listitem>
<para>
The menus on the menubar contain all of the commands you need to
@@ -196,7 +199,8 @@
</para>
</listitem>
</varlistentry>
- <varlistentry> <term>Toolbar</term>
+ <varlistentry>
+ <term>Toolbar</term>
<listitem>
<para>
The toolbar contains the basic debugging actions that can be used
@@ -204,7 +208,8 @@
</para>
</listitem>
</varlistentry>
- <varlistentry> <term>Source View Notebook</term>
+ <varlistentry>
+ <term>Source View Notebook</term>
<listitem>
<para>
When source files are open, this area will display source files of
@@ -212,7 +217,8 @@
</para>
</listitem>
</varlistentry>
- <varlistentry> <term>Status Notebook</term>
+ <varlistentry>
+ <term>Status Notebook</term>
<listitem>
<para>
The Status notebook contains several tabs for displaying
@@ -249,7 +255,7 @@
<listitem>
<para>
If the program being debugged prints any output to the
- terminal, that output will be displayed in this tab.
+ terminal, it will be displayed in this tab.
</para>
</listitem>
</varlistentry>
@@ -265,7 +271,8 @@
right-clicking and selecting <menuchoice><guimenuitem>Go to
Source</guimenuitem></menuchoice> from the menu. In
addition, breakpoints can be deleted, enabled, or disabled
- in this tab.
+ in this tab. For more information about breakpoints, see
+ <xref linkend="nemiver-sect-breakpoints"/>.
</para>
</listitem>
</varlistentry>
@@ -276,8 +283,7 @@
<listitem>
<para>
This tab displays all of the CPU registers and their
- values. For more information, see <xref
- linkend="nemiver-sect-registers"/>.
+ values. For more information, see <xref linkend="nemiver-sect-registers"/>.
</para>
</listitem>
</varlistentry>
@@ -288,8 +294,7 @@
<listitem>
<para>
This tab displays a view of the current state of a specific
- memory location. For more information, see <xref
- linkend="nemiver-sect-memory"/>.
+ memory location. For more information, see <xref linkend="nemiver-sect-memory"/>.
</para>
</listitem>
</varlistentry>
@@ -298,47 +303,47 @@
</varlistentry>
</variablelist>
</sect2>
-
-
- <sect2 id="nemiver-sect-starting-executable">
- <title>Debugging an Executable</title>
-
- <sect3>
- <title>Using the Workbench</title>
- <para>
+ <sect2 id="nemiver-sect-loading-program">
+ <title>Choosing a Program to Debug</title>
+ <para>There are several ways to begin debugging a program. Nemiver
+ allows you to load a local executable file, load a core file, attach
+ to a running process, or connect to a remote debugging server.
+ </para>
+ <sect3 id="nemiver-sect-starting-executable">
+ <title>Debugging an Executable Program</title>
+ <sect4>
+ <title>Using the Workbench</title>
+ <para>
To select an executable program to debug, select
- <menuchoice>
- <guimenu>
+ <menuchoice><guimenu>
File
- </guimenu>
- <guimenuitem>
+ </guimenu><guimenuitem>
Execute...
- </guimenuitem>
- </menuchoice>, which should display the following dialog:
+ </guimenuitem></menuchoice>, which should display the following dialog:
</para>
- <figure id="nemiver-execute-dialog">
- <title>Execute Dialog</title>
- <screenshot>
- <mediaobject>
- <imageobject>
- <imagedata fileref="figures/execute-dialog.png" format="PNG"/>
- </imageobject>
- <textobject> <phrase>Shows dialog for selecting an executable to run</phrase>
- </textobject>
- </mediaobject>
- </screenshot>
- </figure>
- <para>
+ <figure id="nemiver-execute-dialog">
+ <title>Execute Dialog</title>
+ <screenshot>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="figures/execute-dialog.png" format="PNG"/>
+ </imageobject>
+ <textobject>
+ <phrase>Shows dialog for selecting an executable to run</phrase>
+ </textobject>
+ </mediaobject>
+ </screenshot>
+ </figure>
+ <para>
In this dialog, you can select the program to be debugged, any
arguments or options to be passed to the executable on the command line, the
working directory to run the executable in, and any Environment
Variables that should be set when the executable is being debugged.
</para>
- </sect3>
-
- <sect3>
- <title>Using the Command Line</title>
- <para>
+ </sect4>
+ <sect4>
+ <title>Using the Command Line</title>
+ <para>
To start an executable program to debug from the command line, simply
specify the name of the executable. You can either give an absolute
path to the executable, or if it is in the path, you can simply give
@@ -346,70 +351,65 @@
<filename>/usr/bin</filename> is in your path, both of the following
are valid:
</para>
- <itemizedlist>
- <listitem>
- <para>
- <command>&appcmd; /usr/bin/progname</command>
- </para>
- </listitem>
- <listitem>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <command>&appcmd; /usr/bin/progname</command>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <command>&appcmd; progname</command>
+ </para>
+ </listitem>
+ </itemizedlist>
+ <tip>
+ <title>Passing Options on the Command Line</title>
<para>
- <command>&appcmd; progname</command>
- </para>
- </listitem>
- </itemizedlist>
- <tip>
- <title>Passing Options on the Command Line</title>
- <para>
If you would like to pass command line options to the program that
you are debugging, you should enclose them in quotes to prevent
&app; from processing them:
<command>&appcmd; "prognam --arg1 --arg2"</command>.
</para>
- </tip>
+ </tip>
+ </sect4>
</sect3>
-
- </sect2>
-
- <sect2 id="nemiver-sect-attach">
- <title>Attaching to a Running Program</title>
- <sect3>
- <title>Using the Workbench</title>
- <para>
+ <sect3 id="nemiver-sect-attach">
+ <title>Attaching to a Running Program</title>
+ <sect4>
+ <title>Using the Workbench</title>
+ <para>
Select the menu item
- <menuchoice>
- <guimenu>
+ <menuchoice><guimenu>
File
- </guimenu>
- <guimenuitem>
+ </guimenu><guimenuitem>
Attach to Running Program...
- </guimenuitem>
- </menuchoice>, which should display the following dialog:
+ </guimenuitem></menuchoice>, which should display the following dialog:
</para>
- <figure id="nemiver-attach-dialog">
- <title>Attach Dialog</title>
- <screenshot>
- <mediaobject>
- <imageobject>
- <imagedata fileref="figures/attach-dialog.png" format="PNG"/>
- </imageobject>
- <textobject> <phrase>Shows dialog for attaching to a running program</phrase>
- </textobject>
- </mediaobject>
- </screenshot>
- </figure>
- <para>
+ <figure id="nemiver-attach-dialog">
+ <title>Attach Dialog</title>
+ <screenshot>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="figures/attach-dialog.png" format="PNG"/>
+ </imageobject>
+ <textobject>
+ <phrase>Shows dialog for attaching to a running program</phrase>
+ </textobject>
+ </mediaobject>
+ </screenshot>
+ </figure>
+ <para>
Select a process from the list and click
<guibutton>OK</guibutton> to start debugging the selected program.
There may be a lot of processes listed in the dialog, so you can
filter the list to only ones that that you are interested in by typing
some text into the text entry located just below the list.
</para>
- </sect3>
-
- <sect3>
- <title>Using the Command Line</title>
- <para>
+ </sect4>
+ <sect4>
+ <title>Using the Command Line</title>
+ <para>
To attach to a running program from the command line, use the
<option>--attach</option> option. The <option>--attach</option>
option accepts either a pid or a process name. So, for example, to
@@ -417,47 +417,80 @@
1121, you could either type <command>&appcmd; --attach foo</command>
or <command>&appcmd; --attach 1121</command>.
</para>
+ </sect4>
</sect3>
- </sect2>
- <sect2 id="nemiver-sect-core-file">
- <title>Loading a Core File</title>
- <sect3>
- <title>Using the Workbench</title>
- <para>
+ <sect3 id="nemiver-sect-core-file">
+ <title>Loading a Core File</title>
+ <sect4>
+ <title>Using the Workbench</title>
+ <para>
Select the menu item
- <menuchoice>
- <guimenu>
+ <menuchoice><guimenu>
File
- </guimenu>
- <guimenuitem>
+ </guimenu><guimenuitem>
Load Core File...
- </guimenuitem>
- </menuchoice>
+ </guimenuitem></menuchoice>
to bring up the following dialog, which will let you load a core file:
</para>
- <figure id="nemiver-load-core-dialog">
- <title>Load Core File Dialog</title>
+ <figure id="nemiver-load-core-dialog">
+ <title>Load Core File Dialog</title>
+ <screenshot>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="figures/load-core-dialog.png" format="PNG"/>
+ </imageobject>
+ <textobject>
+ <phrase>Shows dialog for loading a core file</phrase>
+ </textobject>
+ </mediaobject>
+ </screenshot>
+ </figure>
+ </sect4>
+ <sect4>
+ <title>Using the Command Line</title>
+ <para>
+ Core files cannot be loaded from the command line.
+ </para>
+ </sect4>
+ </sect3>
+ <sect3 id="nemiver-sect-remote">
+ <title>Remote Debugging</title>
+ <para>
+ &app; allows you to connect to a remote debugging server.
+ </para>
+ <sect4>
+ <title>Using the Workbench</title>
+ <para>
+ To connect to a remote debugging server, select
+ <menuchoice><guimenu>File</guimenu><guimenuitem>Connect to
+ Remote Target...</guimenuitem></menuchoice>
+ </para>
<screenshot>
<mediaobject>
<imageobject>
- <imagedata fileref="figures/load-core-dialog.png" format="PNG"/>
+ <imagedata fileref="figures/connect-remote-dialog.png" format="PNG"/>
</imageobject>
- <textobject> <phrase>Shows dialog for loading a core file</phrase>
+ <textobject>
+ <phrase>Remote Debugging Dialog</phrase>
</textobject>
</mediaobject>
</screenshot>
- </figure>
- </sect3>
-
- <sect3>
- <title>Using the Command Line</title>
- <para>
- Core files cannot be loaded from the command line.
+ <para>
+ Select the executable to load and the location where any shared
+ libraries are located, and then fill in the details about
+ connecting to the remote server.
+ </para>
+ </sect4>
+ <sect4>
+ <title>Using the Command Line</title>
+ <para>
+ &app; does not provide a way to connect to a remote server using
+ the command line
</para>
+ </sect4>
</sect3>
</sect2>
</sect1>
-
<sect1 id="nemiver-sect-using">
<title>Using &app;</title>
<para>
@@ -471,7 +504,8 @@
The most common actions are listed below:
</para>
<variablelist>
- <varlistentry> <term>Continue</term>
+ <varlistentry>
+ <term>Continue</term>
<listitem>
<para>
Starts the program. The program will run until it hits a
@@ -482,7 +516,8 @@
</para>
</listitem>
</varlistentry>
- <varlistentry> <term>Next</term>
+ <varlistentry>
+ <term>Next</term>
<listitem>
<para>
Executes the next statement, and stops when it reaches the next
@@ -492,7 +527,8 @@
</para>
</listitem>
</varlistentry>
- <varlistentry> <term>Step</term>
+ <varlistentry>
+ <term>Step</term>
<listitem>
<para>
Executes the next statement, stepping into the function if possible.
@@ -501,32 +537,29 @@
</para>
</listitem>
</varlistentry>
- <varlistentry> <term>Step Out</term>
+ <varlistentry>
+ <term>Step Out</term>
<listitem>
<para>
Finishes execution of the current function and stops when it
returns to the calling function. This action can be
activated from the keyboard with
- <keycombo>
- <keycap>Shift</keycap>
- <keycap>F7</keycap>
- </keycombo>.
+ <keycombo><keycap>Shift</keycap><keycap>F7</keycap></keycombo>.
</para>
</listitem>
</varlistentry>
- <varlistentry> <term>Restart</term>
+ <varlistentry>
+ <term>Restart</term>
<listitem>
<para>
Reloads the current executable and starts execution from the beginning.
This action can be activated from the keyboard with
- <keycombo>
- <keycap>Shift</keycap>
- <keycap>F5</keycap>
- </keycombo>.
+ <keycombo><keycap>Shift</keycap><keycap>F5</keycap></keycombo>.
</para>
</listitem>
</varlistentry>
- <varlistentry> <term>Stop</term>
+ <varlistentry>
+ <term>Stop</term>
<listitem>
<para>
Manually interrupt execution of the program. This action is only
@@ -541,9 +574,8 @@
By default, after loading an executable, &app; creates a breakpoint at
<function>main()</function>, so when execution reaches
<function>main()</function>, it will stop and wait for input. You can
- then step through the program and examine variables (see <xref
- linkend="nemiver-sect-inspecting-variables"/>), or set breakpoints
- (see <xref linkend="nemiver-sect-breakpoints"/>).
+ then step through the program, examine variables (see <xref linkend="nemiver-sect-inspecting-variables"/>), or set additional
+ breakpoints (see <xref linkend="nemiver-sect-breakpoints"/>).
</para>
</sect2>
<sect2 id="nemiver-sect-inspecting-variables">
@@ -552,10 +584,7 @@
&app; displays a list of all local variables in the
<interface>Variables</interface> tab of the
<interface>Status Notebook</interface>. If you'd like to examine a different variable (or even an arbitrary expression), you can use the <interface>Variable Inspector</interface>. To bring up the <interface>Variable Inspector</interface>, select
- <menuchoice>
- <guimenu>Debug</guimenu>
- <guimenuitem>Inspect a Variable</guimenuitem>
- </menuchoice>. When the variable inspector comes up, you'll see a
+ <menuchoice><guimenu>Debug</guimenu><guimenuitem>Inspect a Variable</guimenuitem></menuchoice>. When the variable inspector comes up, you'll see a
window that looks similar to the following:
</para>
<screenshot>
@@ -563,13 +592,14 @@
<imageobject>
<imagedata fileref="figures/variable-inspector.png" format="PNG"/>
</imageobject>
- <textobject> <phrase>Variable Inspector Dialog</phrase>
+ <textobject>
+ <phrase>Variable Inspector Dialog</phrase>
</textobject>
</mediaobject>
</screenshot>
<para>
You can type any variable name or a simple expression (such as
- <literal>pFoo->bar</literal>) into the input box, and if the variable is
+ <literal>pFoo->bar</literal>) into the input box, and if the variable is
valid and in scope, it will be display details about that expression.
</para>
<para>
@@ -587,27 +617,22 @@
</tip>
<para>
&app; will also let you display a list of all global variables in an application in a separate dialog. To display the <interface>Global Variables</interface> dialog, select
- <menuchoice>
- <guimenu>Debug</guimenu>
- <guimenuitem>Show Global Variables</guimenuitem>
- </menuchoice>
+ <menuchoice><guimenu>Debug</guimenu><guimenuitem>Show Global Variables</guimenuitem></menuchoice>
or press
- <keycombo>
- <keycap>Ctrl</keycap>
- <keycap>G</keycap>
- </keycombo>.
+ <keycombo><keycap>Ctrl</keycap><keycap>G</keycap></keycombo>.
</para>
<screenshot>
- <mediaobject>
- <imageobject>
- <imagedata fileref="figures/global-variables-dialog.png" format="PNG"/>
- </imageobject>
- <textobject> <phrase>Global Variables Dialog</phrase>
- </textobject>
- </mediaobject>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="figures/global-variables-dialog.png" format="PNG"/>
+ </imageobject>
+ <textobject>
+ <phrase>Global Variables Dialog</phrase>
+ </textobject>
+ </mediaobject>
</screenshot>
<warning>
- <para>
+ <para>
For some programs (especially C++ programs), listing all of the
global variables may take a very long time.
</para>
@@ -628,29 +653,21 @@
</listitem>
<listitem>
<para>Place your cursor on a line where you want the breakpoint to be set and set the breakpoint by either selecting
- <menuchoice>
- <guimenu>Debug</guimenu>
- <guimenuitem>Toggle Breakpoint at Cursor</guimenuitem>
- </menuchoice>, or by pressing <keycap>F8</keycap>
+ <menuchoice><guimenu>Debug</guimenu><guimenuitem>Toggle Breakpoint at Cursor</guimenuitem></menuchoice>, or by pressing <keycap>F8</keycap>
</para>
</listitem>
<listitem>
<para>Set a breakpoint at a specific function name or at a specific location in a file by selecting
- <menuchoice>
- <guimenu>Debug</guimenu>
- <guimenuitem>Set Breakpoint...</guimenuitem>
- </menuchoice> or by pressing
- <keycombo>
- <keycap>Ctrl</keycap>
- <keycap>B</keycap>
- </keycombo>. This will bring up a dialog that looks like the following:
+ <menuchoice><guimenu>Debug</guimenu><guimenuitem>Set Breakpoint...</guimenuitem></menuchoice> or by pressing
+ <keycombo><keycap>Ctrl</keycap><keycap>B</keycap></keycombo>. This will bring up a dialog that looks like the following:
</para>
<screenshot>
<mediaobject>
<imageobject>
<imagedata fileref="figures/set-breakpoint-dialog.png" format="PNG"/>
</imageobject>
- <textobject> <phrase>Set Breakpoint Dialog</phrase>
+ <textobject>
+ <phrase>Set Breakpoint Dialog</phrase>
</textobject>
</mediaobject>
</screenshot>
@@ -675,10 +692,7 @@
breakpoint number you want to enable or disable in the
<interface>Breakpoints</interface> tab of the <interface>Status
Notebook</interface>. Alternately, you can press
- <keycombo>
- <keycap>Shift</keycap>
- <keycap>F8</keycap>
- </keycombo> to enable or disable a breakpoint that is set on the
+ <keycombo><keycap>Shift</keycap><keycap>F8</keycap></keycombo> to enable or disable a breakpoint that is set on the
line that the cursor is currently on.
</para>
<para>
@@ -690,7 +704,8 @@
<imageobject>
<imagedata fileref="figures/enabled-breakpoint.png" format="PNG"/>
</imageobject>
- <textobject> <phrase>Illustration of an enabled breakpoint</phrase>
+ <textobject>
+ <phrase>Illustration of an enabled breakpoint</phrase>
</textobject>
<caption>Enabled Breakpoint</caption>
</mediaobject>
@@ -701,7 +716,7 @@
<imagedata fileref="figures/disabled-breakpoint.png" format="PNG"/>
</imageobject>
<textobject>
- <phrase>Illustration of a disabled breakpoint</phrase>
+ <phrase>Illustration of a disabled breakpoint</phrase>
</textobject>
<caption>Disabled Breakpoint</caption>
</mediaobject>
@@ -716,17 +731,15 @@
filesystem, but &app; can also provide a list of source files that
were used to build the executable and allow you to select from this
list. When you select
- <menuchoice>
- <guimenu>File</guimenu>
- <guimenuitem>Open Source File...</guimenuitem>
- </menuchoice>, the following window should be displayed:
+ <menuchoice><guimenu>File</guimenu><guimenuitem>Open Source File...</guimenuitem></menuchoice>, the following window should be displayed:
</para>
<screenshot>
<mediaobject>
<imageobject>
<imagedata fileref="figures/open-files-target.png" format="PNG"/>
</imageobject>
- <textobject> <phrase>Shows dialog for opening source files</phrase>
+ <textobject>
+ <phrase>Shows dialog for opening source files</phrase>
</textobject>
</mediaobject>
</screenshot>
@@ -748,50 +761,52 @@
</sect3>
</sect2>
<sect2 id="nemiver-sect-advanced">
- <title>Advanced Debugging</title>
- <sect3 id="nemiver-sect-registers">
- <title>Registers</title>
- <para>
+ <title>Advanced Debugging</title>
+ <sect3 id="nemiver-sect-registers">
+ <title>Registers</title>
+ <para>
The register editing widget is located in the
<interface>Registers</interface> tab of the <interface>Status
Notebook</interface>. Alternately, you can press
<keycombo><keycap>Alt</keycap><keycap>F5</keycap></keycombo> to
jump directly to the correct tab.
</para>
- <screenshot>
- <mediaobject>
- <imageobject>
- <imagedata fileref="figures/registers-view.png" format="PNG"/>
- </imageobject>
- <textobject> <phrase>The Register Editing Widget</phrase>
- </textobject>
- </mediaobject>
- </screenshot>
- <para>
+ <screenshot>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="figures/registers-view.png" format="PNG"/>
+ </imageobject>
+ <textobject>
+ <phrase>The Register Editing Widget</phrase>
+ </textobject>
+ </mediaobject>
+ </screenshot>
+ <para>
This widget shows the current values of all of the CPU
registers. You can edit the register values by clicking in the
<interface>Value</interface> column and entering a new value.
If the value for the register changed since the last time the
debugger stopped, it will be highlighted in red.
</para>
- </sect3>
- <sect3 id="nemiver-sect-memory">
- <title>Memory</title>
- <para>
+ </sect3>
+ <sect3 id="nemiver-sect-memory">
+ <title>Memory</title>
+ <para>
The memory widget allows you to view a section of memory
directly. This enables you to get a lower-level view of what's
happening while your program is running.
</para>
- <screenshot>
- <mediaobject>
- <imageobject>
- <imagedata fileref="figures/memory-view.png" format="PNG"/>
- </imageobject>
- <textobject> <phrase>The Memory Editing Widget</phrase>
- </textobject>
- </mediaobject>
- </screenshot>
- <para>
+ <screenshot>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="figures/memory-view.png" format="PNG"/>
+ </imageobject>
+ <textobject>
+ <phrase>The Memory Editing Widget</phrase>
+ </textobject>
+ </mediaobject>
+ </screenshot>
+ <para>
To display a segment of memory in the memory view widget, enter
a memory address in the <interface>Address</interface> field.
If the address is valid for the program being debugged, the
@@ -802,37 +817,16 @@
drop-down menu. The memory values will automatically be updated
as you step through the program.
</para>
- <para>
+ <para>
In addition to viewing the memory values, you can also use the
memory widget to modify memory values. You can edit either the
hex byte representation (the left-hand section of the memory
widget), or the ASCII representation (the right-hand section of
the memory widget). All changes will be applied immediately.
</para>
- </sect3>
- <sect3 id="nemiver-sect-remote">
- <title>Remote Debugging</title>
- <para>
- &app; allows you to connect to a remote debugging server. To do
- so, select
- <menuchoice>
- <guimenu>File</guimenu>
- <guimenuitem>Connect to Remote Target...</guimenuitem>
- </menuchoice>
- </para>
- <screenshot>
- <mediaobject>
- <imageobject>
- <imagedata fileref="figures/connect-remote-dialog.png" format="PNG"/>
- </imageobject>
- <textobject> <phrase>Remote Debugging Dialog</phrase>
- </textobject>
- </mediaobject>
- </screenshot>
- </sect3>
+ </sect3>
</sect2>
</sect1>
-
<sect1 id="nemiver-sect-sessions">
<title>Session Save and Restore</title>
<para>
@@ -849,10 +843,7 @@
&app; will save your session automatically on exit, so you don't even
have to worry about it. However, if you want to explicitly save the
session before closing &app;, you can do so by selecting
- <menuchoice>
- <guimenu>File</guimenu>
- <guimenuitem>Save Session To Disk</guimenuitem>
- </menuchoice>.
+ <menuchoice><guimenu>File</guimenu><guimenuitem>Save Session To Disk</guimenuitem></menuchoice>.
</para>
</sect2>
<sect2 id="nemiver-sect-resuming-sessions">
@@ -861,10 +852,7 @@
<title>Using the Workbench</title>
<para>
Select
- <menuchoice>
- <guimenu>File</guimenu>
- <guimenuitem>Resume Saved Session...</guimenuitem>
- </menuchoice>
+ <menuchoice><guimenu>File</guimenu><guimenuitem>Resume Saved Session...</guimenuitem></menuchoice>
and select a session from the list.
</para>
<figure id="nemiver-sessions-dialog">
@@ -874,7 +862,8 @@
<imageobject>
<imagedata fileref="figures/sessions-dialog.png" format="PNG"/>
</imageobject>
- <textobject> <phrase>Shows dialog for resuming a saved session</phrase>
+ <textobject>
+ <phrase>Shows dialog for resuming a saved session</phrase>
</textobject>
</mediaobject>
</screenshot>
@@ -892,23 +881,18 @@
</sect3>
</sect2>
</sect1>
-
<!-- This should be the last section in the manual -->
<sect1 id="nemiver-sect-about">
<title>About &app;</title>
- <para>
- <application>&app;</application> was written by Dodji Seketeli and
+ <para><application>&app;</application> was written by Dodji Seketeli and
Jonathon Jongsma, with contributions from many others. To find more
- information about &app;, please visit the <ulink url="&website;"
- type="http">&app; project website</ulink>.
+ information about &app;, please visit the <ulink url="&website;" type="http">&app; project website</ulink>.
</para>
<para>
To report a bug or make a suggestion regarding this application or this
- manual, see the Feedback section of the <ulink
- url="ghelp:user-guide?feedback-bugs" type="help">GNOME User
+ manual, see the Feedback section of the <ulink url="ghelp:user-guide?feedback-bugs" type="help">GNOME User
Guide</ulink>.
</para>
-
<para>
This program is distributed under the terms of the GNU General Public
license as published by the Free Software Foundation; either version 2 of
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]
