• Top
    • Documentation
    • Books
    • Boolean-reasoning
    • Projects
    • Debugging
    • Community
    • Std
    • Proof-automation
      • Gl
      • Witness-cp
      • Ccg
      • Install-not-normalized
      • Rewrite$
      • Fgl
        • Fgl-rewrite-rules
        • Fgl-function-mode
        • Fgl-object
        • Fgl-solving
        • Fgl-handling-if-then-elses
        • Fgl-counterexamples
        • Fgl-getting-bits-from-objects
        • Fgl-primitive-and-meta-rules
        • Fgl-interpreter-overview
        • Fgl-correctness-of-binding-free-variables
        • Fgl-debugging
        • Fgl-testbenches
        • Def-fgl-boolean-constraint
        • Fgl-stack
        • Def-fgl-param-thm
        • Fgl-rewrite-tracing
          • Fgl-trace
          • Fgl-advanced-tracing
            • Fgl-modify-current-tracespec
            • Fgl-trace*
            • Trace-repl
            • Fgl-untrace*
            • Fgl-untrace-all*
            • Fgl-untrace
            • Fgl-delete-current-tracespec
            • Fgl-untrace-all
          • Def-fgl-thm
          • Fgl-fast-alist-support
          • Fgl-array-support
          • Advanced-equivalence-checking-with-fgl
          • Fgl-fty-support
          • Fgl-internals
        • Removable-runes
        • Efficiency
        • Rewrite-bounds
        • Bash
        • Def-dag-measure
        • Bdd
        • Remove-hyps
        • Contextual-rewriting
        • Simp
        • Rewrite$-hyps
        • Bash-term-to-dnf
        • Use-trivial-ancestors-check
        • Minimal-runes
        • Clause-processor-tools
        • Fn-is-body
        • Without-subsumption
        • Rewrite-equiv-hint
        • Def-bounds
        • Rewrite$-context
        • Try-gl-concls
        • Hint-utils
      • Macro-libraries
      • ACL2
      • Interfacing-tools
      • Hardware-verification
      • Software-verification
      • Math
      • Testing-utilities
    • Fgl-rewrite-tracing

    Fgl-advanced-tracing

    List of advanced things you can do while tracing a rewrite rule in FGL

    See fgl-trace for instructions to set up tracing of a rule. Here we discuss various things you can do with such tracing:

    • Replace the default printing of trace entry/exit forms with your own: returning NIL from the on-entry/on-success/on-failure forms prevents printing of the returned result, and invoking cw or fmt-to-comment-window within the form lets you customize the printing.
    • Abort the application of the rule (cause it to fail) by invoking abort-current-rewrite, even in the :on-success form.
    • Trace rule a only while inside certain applications of rule b by tracing b with the :restore-rules t option and invoking fgl-trace* for rule a within its :on-entry form. (See also fgl-untrace* and fgl-untrace-all*.)
    • Invoke trace-repl to enter a read-eval-print loop where you may interactively examine all the information available in trace forms as well as doing any of the things discussed here.
    • Modify the tracing behavior for the current rule application using fgl-modify-current-tracespec or fgl-delete-current-tracespec, particularly from the trace-repl.