diff options
| author | Jonas Devlieghere <jonas@devlieghere.com> | 2018-11-15 01:18:15 +0000 |
|---|---|---|
| committer | Jonas Devlieghere <jonas@devlieghere.com> | 2018-11-15 01:18:15 +0000 |
| commit | e103ae92ef2336854587778bd3ae88a87e409a5e (patch) | |
| tree | a474b4d1db388480dd129f0ab61a690a4f504ca5 /lldb/scripts | |
| parent | df14b94243e9e8ade2747e6adb8a3d9d2cfa71ae (diff) | |
| download | bcm5719-llvm-e103ae92ef2336854587778bd3ae88a87e409a5e.tar.gz bcm5719-llvm-e103ae92ef2336854587778bd3ae88a87e409a5e.zip | |
Add setting to require hardware breakpoints.
When debugging read-only memory we cannot use software breakpoint. We
already have support for hardware breakpoints and users can specify them
with `-H`. However, there's no option to force LLDB to use hardware
breakpoints internally, for example while stepping.
This patch adds a setting target.require-hardware-breakpoint that forces
LLDB to always use hardware breakpoints. Because hardware breakpoints
are a limited resource and can fail to resolve, this patch also extends
error handling in thread plans, where breakpoints are used for stepping.
Differential revision: https://reviews.llvm.org/D54221
llvm-svn: 346920
Diffstat (limited to 'lldb/scripts')
| -rw-r--r-- | lldb/scripts/interface/SBBreakpoint.i | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/lldb/scripts/interface/SBBreakpoint.i b/lldb/scripts/interface/SBBreakpoint.i index b810682d10f..1383f3848e2 100644 --- a/lldb/scripts/interface/SBBreakpoint.i +++ b/lldb/scripts/interface/SBBreakpoint.i @@ -251,6 +251,9 @@ public: static uint32_t GetNumBreakpointLocationsFromEvent (const lldb::SBEvent &event_sp); + bool + IsHardware (); + %pythoncode %{ class locations_access(object): |
