This is an archive of the discontinued LLVM Phabricator instance.

[dexter] Remove requirement for a condition in DexLimitSteps
ClosedPublic

Authored by Orlando on Apr 28 2021, 3:40 AM.

Details

Summary

Currently the DexLimitSteps command requires at least one condition. This patch lets users elide the condition to specify that the breakpoint range should always be activated when the leading line is stepped on. This patch also updates the terminology used in the ConditionalController class from the terms 'conditional' and 'unconditional' to 'leading' and 'trailing' when referring to the breakpoints in the DexLimitSteps range because the leading breakpoint can now be unconditional.

All the lit tests pass on linux (with lldb), and I've tested this on windows (with vs2017) manually as the lit tests for DexLimitSteps are currently unsupported on windows.

Diff Detail

Event Timeline

Orlando requested review of this revision.Apr 28 2021, 3:40 AM
Orlando created this revision.
Orlando updated this revision to Diff 341479.Apr 29 2021, 5:07 AM

+ Add REQUIRES: system-linux in test (DexLimitSteps has limited support)
+ Rename ConditionalBpRange -> BreakpointRange, cbp -> bpr, *conditional_bp_ranges -> *bp_ranges

This revision is now accepted and ready to land.May 5 2021, 6:24 AM
This revision was landed with ongoing or failed builds.May 17 2021, 1:14 AM
This revision was automatically updated to reflect the committed changes.
Herald added a project: Restricted Project. · View Herald TranscriptMay 17 2021, 1:14 AM