/usr/share/help/gl/anjuta-manual/debug-run.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 | <?xml version="1.0" encoding="utf-8"?>
<page xmlns="http://projectmallard.org/1.0/" type="topic" style="task" id="debug-run" xml:lang="gl">
<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>Iniciar un programa co depurador.</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>Depurar un programa</title>
<section>
<title>Iniciar un programa no depurador.</title>
<p>The current program is defined in the <gui>Program Parameters</gui> dialog.
See <link xref="run-parameters-dialog"/> for more information. This
program can be started in the debugger like this:</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 is missing. Whether optimization and debugging
information are enabled, is defined in the configure step.
Normally, there is a Debug configuration available, that turns off optimization
and includes all debugging information. Anjuta displays a warning
if this configuration is not used.
See <link xref="autotools-build-configure"/> for more information.</p>
</note>
</section>
<section>
<title>Depurar un aplicativo en execución</title>
<p>The debugger can 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 processes.</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>Depurar un aplicativo remoto</title>
<p>The debugger can be used to debug an application running on another
computer connected through a TCP or 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 to the remote application,
<gui>Serial Line Connection</gui> or <gui>TCP/IP Connection</gui>.</p>
</item>
<item>
<p>For a TCP connection, fill in the <gui>Address</gui> and <gui>Port</gui>
fields.</p>
<p>For a serial connection, fill in the text box below with the serial
device name, for 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>Deter o depurador</title>
<p>The debugger and the program can be stopped at any time like this:</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>
|