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
|
//! Add/Remove various kinds of breakpoints.
use crate::arch::Arch;
use crate::target::{Target, TargetResult};
/// Target Extension - Set/Remove Breakpoints.
pub trait Breakpoints: Target {
/// Support for setting / removing software breakpoints.
#[inline(always)]
fn support_sw_breakpoint(&mut self) -> Option<SwBreakpointOps<'_, Self>> {
None
}
/// Support for setting / removing hardware breakpoints.
#[inline(always)]
fn support_hw_breakpoint(&mut self) -> Option<HwBreakpointOps<'_, Self>> {
None
}
/// Support for setting / removing hardware watchpoints.
#[inline(always)]
fn support_hw_watchpoint(&mut self) -> Option<HwWatchpointOps<'_, Self>> {
None
}
}
define_ext!(BreakpointsOps, Breakpoints);
/// Nested Target Extension - Set/Remove Software Breakpoints.
///
/// See [this stackoverflow discussion](https://stackoverflow.com/questions/8878716/what-is-the-difference-between-hardware-and-software-breakpoints)
/// about the differences between hardware and software breakpoints.
///
/// _Recommendation:_ If you're implementing `Target` for an emulator that's
/// using an _interpreted_ CPU (as opposed to a JIT), the simplest way to
/// implement "software" breakpoints would be to check the `PC` value after each
/// CPU cycle, ignoring the specified breakpoint `kind` entirely.
pub trait SwBreakpoint: Target + Breakpoints {
/// Add a new software breakpoint.
///
/// Return `Ok(false)` if the operation could not be completed.
fn add_sw_breakpoint(
&mut self,
addr: <Self::Arch as Arch>::Usize,
kind: <Self::Arch as Arch>::BreakpointKind,
) -> TargetResult<bool, Self>;
/// Remove an existing software breakpoint.
///
/// Return `Ok(false)` if the operation could not be completed.
fn remove_sw_breakpoint(
&mut self,
addr: <Self::Arch as Arch>::Usize,
kind: <Self::Arch as Arch>::BreakpointKind,
) -> TargetResult<bool, Self>;
}
define_ext!(SwBreakpointOps, SwBreakpoint);
/// Nested Target Extension - Set/Remove Hardware Breakpoints.
///
/// See [this stackoverflow discussion](https://stackoverflow.com/questions/8878716/what-is-the-difference-between-hardware-and-software-breakpoints)
/// about the differences between hardware and software breakpoints.
///
/// _Recommendation:_ If you're implementing `Target` for an emulator that's
/// using an _interpreted_ CPU (as opposed to a JIT), there shouldn't be any
/// reason to implement this extension (as software breakpoints are likely to be
/// just-as-fast).
pub trait HwBreakpoint: Target + Breakpoints {
/// Add a new hardware breakpoint.
///
/// Return `Ok(false)` if the operation could not be completed.
fn add_hw_breakpoint(
&mut self,
addr: <Self::Arch as Arch>::Usize,
kind: <Self::Arch as Arch>::BreakpointKind,
) -> TargetResult<bool, Self>;
/// Remove an existing hardware breakpoint.
///
/// Return `Ok(false)` if the operation could not be completed.
fn remove_hw_breakpoint(
&mut self,
addr: <Self::Arch as Arch>::Usize,
kind: <Self::Arch as Arch>::BreakpointKind,
) -> TargetResult<bool, Self>;
}
define_ext!(HwBreakpointOps, HwBreakpoint);
/// The kind of watchpoint that should be set/removed.
#[derive(Clone, Copy, Debug, PartialEq, Eq)]
pub enum WatchKind {
/// Fire when the memory location is written to.
Write,
/// Fire when the memory location is read from.
Read,
/// Fire when the memory location is written to and/or read from.
ReadWrite,
}
/// Nested Target Extension - Set/Remove Hardware Watchpoints.
///
/// See the [GDB documentation](https://sourceware.org/gdb/current/onlinedocs/gdb/Set-Watchpoints.html)
/// regarding watchpoints for how they're supposed to work.
///
/// _Note:_ If this extension isn't implemented, GDB will default to using
/// _software watchpoints_, which tend to be excruciatingly slow (as hey are
/// implemented by single-stepping the system, and reading the watched memory
/// location after each step).
pub trait HwWatchpoint: Target + Breakpoints {
/// Add a new hardware watchpoint.
/// The number of bytes to watch is specified by `len`.
///
/// Return `Ok(false)` if the operation could not be completed.
fn add_hw_watchpoint(
&mut self,
addr: <Self::Arch as Arch>::Usize,
len: <Self::Arch as Arch>::Usize,
kind: WatchKind,
) -> TargetResult<bool, Self>;
/// Remove an existing hardware watchpoint.
/// The number of bytes to watch is specified by `len`.
///
/// Return `Ok(false)` if the operation could not be completed.
fn remove_hw_watchpoint(
&mut self,
addr: <Self::Arch as Arch>::Usize,
len: <Self::Arch as Arch>::Usize,
kind: WatchKind,
) -> TargetResult<bool, Self>;
}
define_ext!(HwWatchpointOps, HwWatchpoint);
|
