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
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
|
# ====================================================================
#
# debug.cdl
#
# Infrastructure debugging configuration data
#
# ====================================================================
## ####ECOSGPLCOPYRIGHTBEGIN####
## -------------------------------------------
## This file is part of eCos, the Embedded Configurable Operating System.
## Copyright (C) 1998, 1999, 2000, 2001, 2002 Free Software Foundation, Inc.
##
## eCos is free software; you can redistribute it and/or modify it under
## the terms of the GNU General Public License as published by the Free
## Software Foundation; either version 2 or (at your option) any later
## version.
##
## eCos is distributed in the hope that it will be useful, but WITHOUT
## ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or
## FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License
## for more details.
##
## You should have received a copy of the GNU General Public License
## along with eCos; if not, write to the Free Software Foundation, Inc.,
## 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.
##
## As a special exception, if other files instantiate templates or use
## macros or inline functions from this file, or you compile this file
## and link it with other works to produce a work based on this file,
## this file does not by itself cause the resulting work to be covered by
## the GNU General Public License. However the source code for this file
## must still be made available in accordance with section (3) of the GNU
## General Public License v2.
##
## This exception does not invalidate any other reasons why a work based
## on this file might be covered by the GNU General Public License.
## -------------------------------------------
## ####ECOSGPLCOPYRIGHTEND####
# ====================================================================
######DESCRIPTIONBEGIN####
#
# Author(s): jskov
# Original data: bartv,hmt
# Contributors:
# Date: 1999-07-02
#
#####DESCRIPTIONEND####
#
# ====================================================================
# If global debugging is enabled then by default all assertions
# are enabled. Tracing is not enabled by default because it
# involves excessive overheads, for example on some targets
# it requires sending a string down a serial line for every
# function call. Both assertions and tracing are controlled
# by the following lines.
cdl_component CYGDBG_USE_ASSERTS {
display "Use asserts"
default_value 1
requires { 1 == CYGINT_INFRA_DEBUG_TRACE_IMPL }
description "
If this option is defined, asserts in the code are tested.
Assert functions (CYG_ASSERT()) are defined in
'include/cyg/infra/cyg_ass.h' within the 'install' tree.
If it is not defined, these result in no additional
object code and no checking of the asserted conditions."
script assert.cdl
}
cdl_component CYGDBG_USE_TRACING {
display "Use tracing"
default_value 0
requires { 1 == CYGINT_INFRA_DEBUG_TRACE_IMPL }
description "
If this option is defined, tracing operations
result in output or logging, depending on other options.
This may have adverse effects on performance, if the time
taken to output message overwhelms the available CPU
power or output bandwidth.
Trace functions (CYG_TRACE()) are defined in
'include/cyg/infra/cyg_trac.h' within the 'install' tree.
If it is not defined, these result in no additional
object code and no trace information."
# The eCos system uses two types of tracing mechanisms. The most common
# type traces events, for example an event could be logged whenever
# an interrupt occurs or whenever a context switch takes place. The
# second type of tracing mechanism records every function entry and
# exit. It is possible to disable this second type of tracing while
# leaving the main tracing facility enabled.
cdl_option CYGDBG_INFRA_DEBUG_FUNCTION_REPORTS {
display "Trace function reports"
default_value 1
description "
This option allows individual control of
function entry/exit tracing, independent of
more general tracing output.
This may be useful to remove clutter from a
trace log."
}
cdl_option CYGDBG_INFRA_DEBUG_TRACE_MESSAGE {
display "Use trace text"
default_value 1
description "
All trace calls within eCos contain a text message
which should give some information about the circumstances.
These text messages will end up being embedded in the
application image and hence there is a significant penalty
in terms of image size.
It is possible to suppress the use of these messages by
disabling this option.
This results in smaller code size, but there is less
human-readable information available in the trace output,
possibly only filenames and line numbers."
}
}
cdl_interface CYGINT_INFRA_DEBUG_TRACE_IMPL {
display "Trace output implementations"
}
cdl_option CYGDBG_INFRA_DEBUG_TRACE_ASSERT_NULL {
display "Null output"
default_value 0
implements CYGINT_INFRA_DEBUG_TRACE_IMPL
description "
A null output module which is useful when
debugging interactively; the output routines
can be breakpointed rather than have them actually
'print' something."
}
cdl_option CYGDBG_INFRA_DEBUG_TRACE_ASSERT_SIMPLE {
display "Simple output"
default_value 0
implements CYGINT_INFRA_DEBUG_TRACE_IMPL
description "
An output module which produces simple output
from tracing and assertion events."
}
cdl_option CYGDBG_INFRA_DEBUG_TRACE_ASSERT_FANCY {
display "Fancy output"
default_value 0
implements CYGINT_INFRA_DEBUG_TRACE_IMPL
description "
An output module which produces fancy output
from tracing and assertion events."
}
cdl_component CYGDBG_INFRA_DEBUG_TRACE_ASSERT_BUFFER {
display "Buffered tracing"
default_value 1
implements CYGINT_INFRA_DEBUG_TRACE_IMPL
description "
An output module which buffers output
from tracing and assertion events. The stored
messages are output when an assert fires, or
CYG_TRACE_PRINT() (defined in <cyg/infra/cyg_trac.h>)
is called.
Of course, there will only be stored messages
if tracing per se (CYGDBG_USE_TRACING)
is enabled above."
cdl_option CYGDBG_INFRA_DEBUG_TRACE_BUFFER_SIZE {
display "Trace buffer size"
flavor data
active_if CYGDBG_USE_TRACING
default_value 32
legal_values 5 to 65535
description "
The size of the trace buffer. This counts the number
of trace records stored. When the buffer fills it
either wraps, stops recording, or generates output."
}
# FIXME: The below options should be mutually exclusive.
cdl_option CYGDBG_INFRA_DEBUG_TRACE_BUFFER_WRAP {
display "Wrap trace buffer when full"
active_if CYGDBG_USE_TRACING
default_value 1
# type radio
description "
When the trace buffer has filled with records it
starts again at the beginning. Hence only the last
CYGDBG_INFRA_DEBUG_TRACE_BUFFER_SIZE messages will
be recorded."
}
cdl_option CYGDBG_INFRA_DEBUG_TRACE_BUFFER_HALT {
display "Halt trace buffer when full"
active_if CYGDBG_USE_TRACING
default_value 0
# type radio
description "
When the trace buffer has filled with records it
stops recording. Hence only the first
CYGDBG_INFRA_DEBUG_TRACE_BUFFER_SIZE messages will
be recorded."
}
cdl_option CYGDBG_INFRA_DEBUG_TRACE_BUFFER_PRINT {
display "Print trace buffer when full"
active_if CYGDBG_USE_TRACING
default_value 0
# type radio
description "
When the trace buffer has filled with records it
prints the contents of the buffer. The buffer is then
emptied and the system continues."
}
cdl_option CYGDBG_INFRA_DEBUG_TRACE_BUFFER_PRINT_ON_ASSERT {
display "Print trace buffer on assert fail"
active_if CYGDBG_USE_TRACING
default_value 1
description "
When an assertion fails the trace buffer will be
printed to the default diagnostic device."
}
}
cdl_option CYGDBG_INFRA_DEBUG_FUNCTION_PSEUDOMACRO {
display "Use function names"
default_value 1
description "
All trace and assert calls within eCos contain a
reference to the builtin macro '__PRETTY_FUNCTION__',
which evaluates to a string containing
the name of the current function.
This is useful when reading a trace log.
It is possible to suppress the use of the function name
by disabling this option.
This results in smaller code size, but there is less
human-readable information available in the trace output,
possibly only filenames and line numbers."
}
|
