package coq-core

  1. Overview
  2. Docs
The Coq Proof Assistant -- Core Binaries and Tools

Install

Dune Dependency

Authors

Maintainers

Sources

coq-8.18.0.tar.gz
md5=8d852367b54f095d9fbabd000304d450
sha512=46922d5f2eb6802a148a52fd3e7f0be8370c93e7bc33cee05cf4a2044290845b10ccddbaa306f29c808e7c5019700763e37e45ff6deb507b874a4348010fed50

doc/coq-core.vernac/DebugHook/Action/index.html

Module DebugHook.ActionSource

The debugger receives requests by calling read_cmd to get Actions. Each Action may return one or more responses as Answers by calling submit_answer. Many of them return a single Answer or no Answer, but a single step may generate any number of Outputs.

Debugger initialization has the following steps: -> Coq sends Answer.Init <- IDE sends zero or more initialization requests such as Action.UpdBpts <- IDE sends Action.Configd

Stopping in the debugger generates Answer.Prompt and Answer.Goal messages, at which point the IDE will typically call GetStack and GetVars. When the IDE sends with StepIn..Continue, the debugger will execute more code. At that point, Coq won't try to read more messages from the IDE until the debugger stops again or exits.

Sourcetype t =
  1. | StepIn
  2. | StepOver
  3. | StepOut
  4. | Continue
  5. | Skip
  6. | Interrupt
  7. | Help
  8. | UpdBpts of ((string * int) * bool) list
  9. | Configd
  10. | GetStack
  11. | GetVars of int
  12. | RunCnt of int
  13. | RunBreakpoint of string
  14. | Command of string
  15. | Failed
  16. | Ignore
Sourceval parse : string -> (t, string) result
OCaml

Innovation. Community. Security.