OpenCores
URL https://opencores.org/ocsvn/or1k/or1k/trunk

Subversion Repositories or1k

[/] [or1k/] [trunk/] [insight/] [gdb/] [gdbtcl/] [help/] [trace/] [tracedlg.html] - Blame information for rev 1767

Go to most recent revision | Details | Compare with Previous | View Log

Line No. Rev Author Line
1 578 markom
<HTML>
2
<HEAD>
3
<TITLE>Tracepoint Dialogs Help</TITLE>
4
</HEAD>
5
<BODY>
6
<H1>Tracepoint Dialogs</H1>
7
<H3>Overview</H3>
8
<P>There are two Tracepoint Dialogs which help users set tracepoints:
9
The Tracepoint Dialog is used to view and add actions and The Actions
10
Dialog is used to edit a particular action specified in the
11
tracepoint's Action List.</P>
12
 
13
<P>Tracepoint Dialogs topics:
14
<UL>
15
    <LI><A HREF="#tracedlg">The Tracepoint Dialog</A>
16
        <UL>
17
            <LI><A HREF="#t_experiment">Experiment Frame</A>
18
            <LI><A HREF="#t_actions">Actions Frame</A>
19
                 <UL>
20
                     <LI><A HREF="#t_actions_passcount">Number of Passes</A>
21
                     <LI><A HREF="#t_actions_add">Adding Actions</A>
22
                     <LI><A HREF="#t_actions_modify">Modifying Actions</A>
23
                 </UL>
24
         </UL>
25
     <LI><A HREF="#actionsdlg">The Actions Dialog</A>
26
         <UL>
27
             <LI><A HREF="#a_variables">Variables List</A>
28
             <LI><A HREF="#a_collect">Collection List</A>
29
             <LI><A HREF="#a_other">Other Entry</A>
30
         </UL>
31
</UL></P>
32
 
33
<H3><A NAME="tracedlg">The Tracepoint Dialog</H3>
34
The Tracepoint Dialog is the gateway to viewing and editing
35
the properties of any tracepoint. The same dialog is used
36
to add new tracepoints and edit and delete existing tracepoints,
37
for both single tracepoints and ranges of tracepoints.
38
 
39
<H4><A NAME="t_experiment">Experiment Frame</A></H4>
40
The Experiment Frame displays information about the tracepoint's
41
location in the program and its status. Specifically,
42
<DL>
43
    <DT>Number
44
        <DD>The internal number for this tracepoint. New tracepoints
45
            all have the number "-1". This number may be used to
46
            refer to specific tracepoints when using the
47
            <A HREF="console.html">Console Window</A>
48
    <DT>Hit Count
49
        <DD>The number of times the tracepoint has been hit
50
    <DT>Thread
51
        <DD>The thread in which the tracepoint exists. This
52
            feature is not currently implemented.
53
    <DT>Function
54
        <DD>The function in which the tracepoint is set
55
    <DT>File
56
        <DD>The file in which the tracepoint is set
57
    <DT>Line(s)
58
        <DD>The line at which the tracepoint is set or the
59
            lines which the tracepoint range affects
60
</DL>
61
<BR>
62
 
63
<H4><A NAME="t_actions">Actions Frame</A></H4>
64
The Actions Frame displays the user-settable properties of the
65
tracepoint, including all actions and a pass count.
66
 
67
<P>A pass count specifies the number of times that the tracepoint
68
can be hit on the target before the tracing experiment ceases. A
69
pass count of five means that this tracepoint will issue a silent
70
"tstop" when it is hit the fifth time (after it has performed all
71
it actions). A pass count of zero (0) means that the tracepoint
72
will never causes the trace experiment to terminate on the target.</P>
73
 
74
<P>To <A NAME="t_actions_add">add an action</A> for the tracepoint,
75
select the appropriate action from the Action ComboBox and click
76
"Add". The <A HREF="#actionsdlg">Action Dialog</A> appears to
77
allow editing the action's properties.</P>
78
 
79
<P>Currently, there are two actions: collect and while-stepping.
80
Any number of collect actions may be added to specify that the
81
target should collect variables, registers, and memory when
82
it is hit. The while-stepping action may be used to collect
83
data for a specified number of machine instructions. Only one
84
while-stepping action may be specified for any tracepoint.</P>
85
 
86
<P>To <A NAME="t_actions_modify">modify the actions</A> associated
87
with a tracepoint, double-click the left mouse button on the action
88
listed in the Action Frame, and the <A HREF="#actionsdlg">Actions
89
Dialog</A> will appear.</P>
90
 
91
<P>To accept the tracepoint as displayed, click the OK button. To abort
92
installing or editing the tracepoint, click the CANCEL button. To delete
93
the tracepoint (if it is not a new tracepoint), click the DELETE button.</P>
94
 
95
<H3><A NAME="actionsdlg">The Actions Dialog</A></H3>
96
The Actions Dialog is used to edit an action for the tracepoint. It
97
consists of two lists, one containing all (uncollected) local variables
98
(including function arguments) and registers, and one containing everything
99
being collected.
100
 
101
<P>The <A NAME="#a_variables">Variables List</A> lists all uncollected local variables,
102
function arguments, and registers  and may also display the special indentifiers
103
"All Locals", "All Arguments", and "All Registers". Global variables (and file static
104
variables) do not appear on the Variable List.</P>
105
 
106
<P>To move a variable from the Variables List to the Collection List, double-click
107
the variable in the Variables List or select the variable in the Variable
108
List and press the "<<< Collect" button. To specify a range of variables to be
109
collected, select them in the Variables list and click the "<<< Collect" button.</P>
110
 
111
<P><A NAME="a_collect">The Collection List displays all data being collected
112
by the action, including the special types "All Locals", "All Registers", and
113
"All Arguments", which specify that every local variable, every register, and
114
every function argument will be collected, respectively. Specifying a local
115
variable, for example, and "All Locals" will cause only the special identifier
116
"All Locals" to be sent to the target. Analogously, "All Registers" and "All
117
Arguments" also override any register or function argument specifically listed
118
in the Collection List.</P>
119
 
120
<P>To remove data from the Collection List, double-click any of the entries listed
121
in the List, or select a range of data to be removed and press the "Ignore >>>"
122
button. All local variables, function arguments, registers, and special identifiers
123
will be returned to the Variable List, while any expression (memory ranges, globals)
124
will simply "disappear". To add these again, use the <A HREF="#a_other">Other Entry</A>
125
at the bottom of the display.</P>
126
 
127
<P>The <A NAME="#a_other">Other Entry</A> can be used to move any variable listed in
128
either the Collection List or the Variable List to the other list. It can also
129
be used to specify expressions for collection, such as memory ranges and global variables.
130
Simply enter the name of the global variable or the expression and press the enter key on
131
the keyboard. If the expression is valid, it will be added/removed from the Collection
132
List.</P>
133
</BODY>
134
</HTML>

powered by: WebSVN 2.1.0

© copyright 1999-2024 OpenCores.org, equivalent to Oliscience, all rights reserved. OpenCores®, registered trademark.