package dap

  1. Overview
  2. Docs
Debug adapter protocol

Install 

dune-project
 Dependency

github.com Edit opam file Versions (8)

Authors

  1. æ
    文宇祥 <hackwaly@qq.com>

Maintainers

  1. æ
    文宇祥 <hackwaly@qq.com>

Sources

dap-1.1.0.tbz
sha256=0b4cdef2ec61b98f73b686a6cb9cde8dde14404097f52a9367c55f1667441712
sha512=ba1897e3afa66b34ad65911dee0b433c48756a5c81467b6277cc2fc1f4360533af7c707744b87707afa9891886dcdb0f7fa7e1653807903f5bd2c1d36a4d92d0

doc/dap.types/Debug_protocol/Variable/index.html

Module Debug_protocol.VariableSource

Sourcetype t = {
  1. name : string;
    (*

    The variable's name.

    *)
  2. value : string;
    (*

    The variable's value. This can be a multi-line text, e.g. for a function the body of a function. For structured variables (which do not have a simple value), it is recommended to provide a one-line representation of the structured object. This helps to identify the structured object in the collapsed state when its children are not yet visible. An empty string can be used if no value should be shown in the UI.

    *)
  3. type_ : string option;
    (*

    The type of the variable's value. Typically shown in the UI when hovering over the value. This attribute should only be returned by a debug adapter if the corresponding capability `supportsVariableType` is true.

    *)
  4. presentation_hint : Variable_presentation_hint.t option;
    (*

    Properties of a variable that can be used to determine how to render the variable in the UI.

    *)
  5. evaluate_name : string option;
    (*

    The evaluatable name of this variable which can be passed to the `evaluate` request to fetch the variable's value.

    *)
  6. variables_reference : int;
    (*

    If `variablesReference` is > 0, the variable is structured and its children can be retrieved by passing `variablesReference` to the `variables` request as long as execution remains suspended. See 'Lifetime of Object References' in the Overview section for details.

    *)
  7. named_variables : int option;
    (*

    The number of named child variables. The client can use this information to present the children in a paged UI and fetch them in chunks.

    *)
  8. indexed_variables : int option;
    (*

    The number of indexed child variables. The client can use this information to present the children in a paged UI and fetch them in chunks.

    *)
  9. memory_reference : string option;
    (*

    A memory reference associated with this variable. For pointer type variables, this is generally a reference to the memory address contained in the pointer. For executable data, this reference may later be used in a `disassemble` request. This attribute may be returned by a debug adapter if corresponding capability `supportsMemoryReferences` is true.

    *)
  10. declaration_location_reference : int option;
    (*

    A reference that allows the client to request the location where the variable is declared. This should be present only if the adapter is likely to be able to resolve the location.

    This reference shares the same lifetime as the `variablesReference`. See 'Lifetime of Object References' in the Overview section for details.

    *)
  11. value_location_reference : int option;
    (*

    A reference that allows the client to request the location where the variable's value is declared. For example, if the variable contains a function pointer, the adapter may be able to look up the function's location. This should be present only if the adapter is likely to be able to resolve the location.

    This reference shares the same lifetime as the `variablesReference`. See 'Lifetime of Object References' in the Overview section for details.

    *)
  12. __vscode_variable_menu_context : string option;
}

A Variable is a name/value pair. The `type` attribute is shown if space permits or when hovering over the variable's name. The `kind` attribute is used to render additional properties of the variable, e.g. different icons can be used to indicate that a variable is public or private. If the value is structured (has children), a handle is provided to retrieve the children with the `variables` request. If the number of named or indexed children is large, the numbers should be returned via the `namedVariables` and `indexedVariables` attributes. The client can use this information to present the children in a paged UI and fetch them in chunks.

Sourceval make : name:string -> value:string -> ?type_:string option -> ?presentation_hint:Variable_presentation_hint.t option -> ?evaluate_name:string option -> variables_reference:int -> ?named_variables:int option -> ?indexed_variables:int option -> ?memory_reference:string option -> ?declaration_location_reference:int option -> ?value_location_reference:int option -> ?__vscode_variable_menu_context:string option -> unit -> t
Sourceval to_yojson : t -> Yojson.Safe.t