package dap

  1. Overview
  2. Docs
Debug adapter protocol

Install

dune-project
 Dependency

Authors

Maintainers

Sources

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

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

Module Debug_protocol.ModuleSource

Sourcetype t = {
  1. id : Int_or_string.t;
    (*

    Unique identifier for the module.

    *)
  2. name : string;
    (*

    A name of the module.

    *)
  3. path : string option;
    (*

    Logical full path to the module. The exact definition is implementation defined, but usually this would be a full path to the on-disk file for the module.

    *)
  4. is_optimized : bool option;
    (*

    True if the module is optimized.

    *)
  5. is_user_code : bool option;
    (*

    True if the module is considered 'user code' by a debugger that supports 'Just My Code'.

    *)
  6. version : string option;
    (*

    Version of Module.

    *)
  7. symbol_status : string option;
    (*

    User-understandable description of if symbols were found for the module (ex: 'Symbols Loaded', 'Symbols not found', etc.)

    *)
  8. symbol_file_path : string option;
    (*

    Logical full path to the symbol file. The exact definition is implementation defined.

    *)
  9. date_time_stamp : string option;
    (*

    Module created or modified, encoded as a RFC 3339 timestamp.

    *)
  10. address_range : string option;
    (*

    Address range covered by this module.

    *)
}

A Module object represents a row in the modules view. The `id` attribute identifies a module in the modules view and is used in a `module` event for identifying a module for adding, updating or deleting. The `name` attribute is used to minimally render the module in the UI.

Additional attributes can be added to the module. They show up in the module view if they have a corresponding `ColumnDescriptor`.

To avoid an unnecessary proliferation of additional attributes with similar semantics but different names, we recommend to re-use attributes from the 'recommended' list below first, and only introduce new attributes if nothing appropriate could be found.

Sourceval make : id:Int_or_string.t -> name:string -> ?path:string option -> ?is_optimized:bool option -> ?is_user_code:bool option -> ?version:string option -> ?symbol_status:string option -> ?symbol_file_path:string option -> ?date_time_stamp:string option -> ?address_range:string option -> unit -> t
Sourceval to_yojson : t -> Yojson.Safe.t