Kinds of special `write_debug` messages the profiler can handle. Messages are of the form `__wasm_debugger__::<debug_call>(<data>)`
type t = private {mutable call_stack : function_call call_stack * function_call call_stack list;mutable kernel_runs : function_call call_stack option list;mutable sections : (Z.t * string) list;mutable debug_call : debug_call option;}The profiling state is the internal state built by the profiler. It is defined as mutable as it is updated by side effects during the profiling.
type should_compute :=
Tezos_scoru_wasm.Wasm_pvm_state.Internal_state.pvm_state ->
bool Lwt.tval init :
symbols:string Custom_section.FuncMap.t ->
with_time:bool ->
reveal_builtins:Tezos_scoru_wasm.Builtins.reveals option ->
write_debug:Tezos_scoru_wasm.Builtins.write_debug option ->
t * should_compute * Tezos_scoru_wasm.Builtins.write_debug optioninit ~symbols ~current_time initializes the profiler state and returns the instrumented `should_compute` function expected by the WASM PVM and the instrumented `write_debug` backend. This function updates the profiler state by side effects during the compilation.
val finalized_runs : t -> function_call call_stack option list