• Top
  • Documentation
  • Books
  • Boolean-reasoning
  • Projects
  • Debugging
    • Break-rewrite
      • Monitor
      • Brr
      • Brr-commands
      • Dmr
      • With-brr-data
      • Geneqv
      • Refinement-failure
      • Break-lemma
      • Why-brr
      • Brr@
      • Cw-gstack
      • Ok-if
      • Windows-installation
      • Brr-near-missp
      • Monitored-runes
      • Unmonitor
      • Monitor!
    • Proof-builder
    • Accumulated-persistence
    • Cgen
    • Forward-chaining-reports
    • Proof-tree
    • Print-gv
    • Dmr
    • With-brr-data
    • Splitter
    • Guard-debug
    • Set-debugger-enable
    • Redo-flat
    • Time-tracker
    • Set-check-invariant-risk
    • Removable-runes
    • Efficiency
    • Explain-near-miss
    • Tail-biting
    • Failed-forcing
    • Sneaky
    • Invariant-risk
    • Failure
    • Measure-debug
    • Dead-events
    • Compare-objects
    • Prettygoals
    • Remove-hyps
    • Type-prescription-debugging
    • Pstack
    • Trace
    • Set-register-invariant-risk
    • Walkabout
    • Disassemble$
    • Nil-goal
    • Cw-gstack
    • Set-guard-msg
    • Find-lemmas
    • Watch
    • Quick-and-dirty-subsumption-replacement-step
    • Profile-all
    • Profile-ACL2
    • Set-print-gv-defaults
    • Minimal-runes
    • Spacewalk
    • Try-gl-concls
    • Near-misses
  • Std
  • Proof-automation
  • Macro-libraries
  • ACL2
  • Interfacing-tools
  • Hardware-verification
  • Software-verification
  • Math
  • Testing-utilities

• Break-rewrite

Monitor!

A quiet combination of monitor and brr

Monitor! is essentially the corresponding call of monitor preceded by (brr t), but avoiding output. See monitor and see brr.

Note that monitor! may be used in place of monitor even when inside an interactive break from break-rewrite; in that case, the brr invocation on its behalf is essentially redundant.