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
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
//! Patina Debugger
//!
//! This crate provides a debugger implementation that will install itself in the
//! exception handlers and communicate with debugger software using the GDB Remote
//! protocol. The debugger is intended to be used in the boot phase cores.
//!
//! This crate is under construction and may be missing functionality, documentation,
//! and testing.
//!
//! ## Getting Started
//!
//! For more details on using the debugger on a device, see the [readme](./Readme.md).
//!
//! ## Examples and Usage
//!
//! The debugger consists of the static access routines and the underlying debugger
//! struct. The top level platform code should initialize the static `PatinaDebugger`
//! struct with the appropriate serial transport and default configuration. The
//! platform has the option of setting static configuration, or enabling the
//! debugger in runtime code based on platform policy. During entry, the platform
//! should use the `set_debugger` routine to set the global instance of the debugger.
//!
//! Core code should use the static routines to interact with the debugger. If the
//! debugger is either not set or not enabled, the static routines will be no-ops.
//!
//! ```rust
//! extern crate patina;
//! # extern crate patina_internal_cpu;
//! # use patina_internal_cpu::interrupts::{Interrupts, InterruptManager};
//! # use patina::component::service::perf_timer::ArchTimerFunctionality;
//!
//! static DEBUGGER: patina_debugger::PatinaDebugger<patina::serial::uart::UartNull> =
//! patina_debugger::PatinaDebugger::new(patina::serial::uart::UartNull{})
//! .with_timeout(30); // Set initial break timeout to 30 seconds.
//!
//! fn entry() {
//!
//! // Configure the debugger. This is used for dynamic configuration of the debugger.
//! DEBUGGER.enable(true);
//!
//! // Set the global debugger instance. This can only be done once.
//! patina_debugger::set_debugger(&DEBUGGER);
//!
//! // Setup a custom monitor command for this platform.
//! patina_debugger::add_monitor_command("my_command", "Description of my_command", |args, writer| {
//! // Parse the arguments from _args, which is a SplitWhitespace iterator.
//! let _ = write!(writer, "Executed my_command with args: {:?}", args);
//! });
//!
//! // Call the core entry. The core can then initialize and access the debugger
//! // through the static routines.
//! start();
//! }
//!
//! fn start() {
//! // Initialize the debugger. This will cause a debug break because of the
//! // initial break configuration set above.
//! patina_debugger::initialize(&mut Interrupts::default(), Some(&ExampleTimer));
//!
//! // Notify the debugger of a module load.
//! patina_debugger::notify_module_load("module.efi", 0x420000, 0x10000);
//!
//! // Poll the debugger for any pending interrupts.
//! patina_debugger::poll_debugger();
//!
//! // Break into the debugger if the debugger is enabled and initialized.
//! patina_debugger::breakpoint();
//!
//! // Cause a debug break unconditionally. This will crash the system
//! // if the debugger is not enabled or initialized. This should be used with extreme caution.
//! patina_debugger::breakpoint_unchecked();
//! }
//!
//! # struct ExampleTimer;
//! # impl ArchTimerFunctionality for ExampleTimer {
//! # fn cpu_count(&self) -> u64 {
//! # 0
//! # }
//! #
//! # fn perf_frequency(&self) -> u64 {
//! # 1
//! # }
//! # }
//!
//! ```
//!
//! The debugger can be further configured by using various functions on the
//! initialization of the debugger struct. See the definition for [debugger::PatinaDebugger]
//! for more details. Notably, if the device is using the same transport for
//! logging and debugger, it is advisable to use `.without_log_init()`.
//!
//! ## Features
//!
//! `alloc` - Uses allocated buffers rather than static buffers for all memory. This provides additional functionality
//! but prevents debugging prior to allocations being available. This is intended for use by the core crate, and not
//! for platform use.
//!
//! ## License
//!
//! Copyright (C) Microsoft Corporation.
//!
//! SPDX-License-Identifier: Apache-2.0
//!
// The debugger needs integration test infrastructure. Disabling coverage until this is completed.
// The debugger needs integration test infrastructure. Disabling coverage until this is completed.
// The debugger needs integration test infrastructure. Disabling coverage until this is completed.
extern crate alloc;
pub use PatinaDebugger;
use ;
use ;
use ;
/// Global instance of the debugger.
///
/// This is only expected to be set once, and will be accessed through the static
/// routines after that point. Because the debugger is expected to install itself
/// in exception handlers and will have access to other static state for things
/// like breakpoints, it is not safe to remove or replace it. For this reason,
/// this uses the Once lock to provide these properties.
///
static DEBUGGER: Once = new;
/// Type for monitor command functions. This will be invoked by the debugger when
/// the associated monitor command is invoked.
///
/// The first argument contains the whitespace separated arguments from the command.
/// For example, if the command is `my_command arg1 arg2`, then `arg1` and `arg2` will
/// be the first and second elements of the iterator respectively.
///
/// The second argument is a writer that should be used to write the output of the
/// command. This can be done by directly invoking the [core::fmt::Write] trait methods
/// or using the `write!` macro. `format!` should be avoided as it will allocate memory
/// which shouldn't be done in debugger when possible.
pub type MonitorCommandFn = dyn Fn + Send + Sync;
/// Trait for debugger interaction. This is required to allow for a global to the
/// platform specific debugger implementation. For safety, these routines should
/// only be invoked on the global instance of the debugger.
/// Policy for how the debugger will handle logging on the system.
/// Sets the global instance of the debugger.
/// Initializes the debugger. This will install the debugger into the exception
/// handlers using the provided interrupt manager. This routine may invoke a debug
/// break depending on configuration.
// Initializing the debugger requires integration testing infrastructure. Disabling coverage until this is completed.
/// Invokes a debug break instruction if the debugger is enabled and initialized. This will cause
/// the debugger to break in. If the debugger is not enabled and initialized, this routine will have no effect.
/// Invokes a debug break instruction unconditionally. If this routine is invoked when
/// the debugger is not enabled and initialized, it will cause an unhandled exception.
///
/// ## Important
///
/// This should only be used in debug scenarios or when it is impossible to continue
/// execution in the current state and an CPU exception must be raised.
/// Notifies the debugger of a module load at the provided address and length.
/// This should be invoked before the module has begun execution.
/// Polls the debugger for any pending interrupts. The routine may cause a debug
/// break.
/// Checks if the debugger is enabled.
/// Checks if the debugger is initialized.
/// Adds a monitor command to the debugger. This may be called before initialization,
/// but should not be called before memory allocations are available. See [MonitorCommandFn]
/// for more details on the callback function expectations.
///
/// ## Example
///
/// ```rust
/// patina_debugger::add_monitor_command("my_command", "Description of my_command", |args, writer| {
/// // Parse the arguments from _args, which is a SplitWhitespace iterator.
/// let _ = write!(writer, "Executed my_command with args: {:?}", args);
/// });
/// ```
///
/// Adds a monitor command to the debugger. This may be called before initialization,
/// but should not be called before memory allocations are available. See [MonitorCommandFn]
/// for more details on the callback function expectations.
///
/// ## Example
///
/// ```rust
/// patina_debugger::add_monitor_command("my_command", "Description of my_command", |args, writer| {
/// // Parse the arguments from _args, which is a SplitWhitespace iterator.
/// let _ = write!(writer, "Executed my_command with args: {:?}", args);
/// });
/// ```
///
/// Exception information for the debugger.
/// Exception type information.