mirror of
https://github.com/intel/llvm.git
synced 2026-01-16 05:32:28 +08:00
3692267ca8
Watchpoints in lldb can be either 'read', 'write', or 'read/write'. This is exposing the actual behavior of hardware watchpoints. gdb has a different behavior: a "write" type watchpoint only stops when the watched memory region *changes*. A user is using a watchpoint for one of three reasons: 1. Want to find what is changing/corrupting this memory. 2. Want to find what is writing to this memory. 3. Want to find what is reading from this memory. I believe (1) is the most common use case for watchpoints, and it currently can't be done in lldb -- the user needs to continue every time the same value is written to the watched-memory manually. I think gdb's behavior is the correct one. There are some use cases where a developer wants to find every function that writes/reads to/from a memory region, regardless of value, I want to still allow that functionality. This is also a bit of groundwork for my large watchpoint support proposal https://discourse.llvm.org/t/rfc-large-watchpoint-support-in-lldb/72116 where I will be adding support for AArch64 MASK watchpoints which watch power-of-2 memory regions. A user might ask to watch 24 bytes, and a MASK watchpoint stub can do this with a 32-byte MASK watchpoint if it is properly aligned. And we need to ignore writes to the final 8 bytes of that watched region, and not show those hits to the user. This patch adds a new 'modify' watchpoint type and it is the default. rdar://108234227
13 lines
1000 B
OpenEdge ABL
13 lines
1000 B
OpenEdge ABL
%feature("docstring",
|
|
"A container for options to use when creating watchpoints."
|
|
) lldb::SBWatchpointOptions;
|
|
|
|
%feature("docstring", "Sets whether the watchpoint should stop on read accesses."
|
|
) lldb::SBWatchpointOptions::SetWatchpointTypeRead;
|
|
%feature("docstring", "Gets whether the watchpoint should stop on read accesses."
|
|
) lldb::SBWatchpointOptions::GetWatchpointTypeRead;
|
|
%feature("docstring", "Sets whether the watchpoint should stop on write accesses. eWatchpointWriteTypeOnModify is the most commonly useful mode, where lldb will stop when the watched value has changed. eWatchpointWriteTypeAlways will stop on any write to the watched region, even if it's the value is the same."
|
|
) lldb::SBWatchpointOptions::SetWatchpointTypeWrite;
|
|
%feature("docstring", "Gets whether the watchpoint should stop on write accesses, returning WatchpointWriteType to indicate the type of write watching that is enabled, or eWatchpointWriteTypeDisabled."
|
|
) lldb::SBWatchpointOptions::GetWatchpointTypeWrite;
|