[all-commits] [llvm/llvm-project] e35a54: [dexter] Remove requirement for a condition in Dex...

[Orlando Cazalet-Hyams via All-commits]

  Branch: refs/heads/main
  Home:   https://github.com/llvm/llvm-project
  Commit: e35a5492a46d419478daf65eeaed5036cfcfa3e5
      https://github.com/llvm/llvm-project/commit/e35a5492a46d419478daf65eeaed5036cfcfa3e5
  Author: OCHyams <orlando.hyams at sony.com>
  Date:   2021-05-17 (Mon, 17 May 2021)

  Changed paths:
    M debuginfo-tests/dexter/Commands.md
    M debuginfo-tests/dexter/dex/command/commands/DexLimitSteps.py
    M debuginfo-tests/dexter/dex/debugger/DebuggerControllers/ConditionalController.py
    A debuginfo-tests/dexter/feature_tests/commands/perfect/limit_steps/unconditional.cpp
    A debuginfo-tests/dexter/feature_tests/subtools/test/err_limit_steps_no_values.cpp

  Log Message:
  -----------
  [dexter] Remove requirement for a condition in DexLimitSteps

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.

Reviewed By: chrisjackson

Differential Revision: https://reviews.llvm.org/D101438