/usr/share/help/th/anjuta-manual/debug-stack.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 | <?xml version="1.0" encoding="utf-8"?>
<page xmlns="http://projectmallard.org/1.0/" type="topic" style="task" id="debug-stack" xml:lang="th">
<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 the stack.
</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>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.
You can only view the stack frames while the debugger is running.</p>
<p>Moreover, a program can be composed of several threads. Each thread is
executed independently and has its own registers, stack and local
variables, but shares all global variables.</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>The stacks are displayed in a tree view having their corresponding
thread as parent and displaying 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 frame 0, the current function. All evaluations and
local variables are relative to this active frame. You can change
the active stack frame to examine local variables in other functions.</p>
</item>
<item>
<title>เธรด</title>
<p>This is a number corresponding to each thread.</p>
</item>
<item>
<title>Frame</title>
<p>This is the frame number starting from 0 for the current function.
The first function of your program, for example <code>main()</code> in a C program,
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>แอดเดรส</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 the current stack frame or thread</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>
<p>Clicking on a stack frame in the same thread changes only the
stack frame, allowing to see other local variables. But doing it
in another thread will change both the stack frame
and the thread. The register values will be different and the
debugger will restart in the selected thread.</p>
</section>
<section>
<title>View the 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>
|