75e8620778
This reverts commit a7b78cac9a.
With updates to the tests.
TestWatchTaggedAddress.py: Updated the expected watchpoint types,
though I'm not sure there should be a differnt default for the two
ways of setting them, that needs to be confirmed.
TestStepOverWatchpoint.py: Skipped this everywhere because I think
what used to happen is you couldn't put 2 watchpoints on the same
address (after alignment). I guess that this is now allowed because
modify watchpoints aren't accounted for, but likely should be.
Needs investigating.
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;
|