Make a runtime introspection tool for investigating all sorts of runtime related details

[nagisa]

Today the runtime is an entirely opaque box to the users of the runtime. Users call a run function and things will supposedly happen.

This API leaves very little space to actually get any information back from the VM, which makes investigating issues with the runtime an extremely menial ordeal.

I would like to have a CLI tool which would allow for people working on the contract runtime to invoke and introspect the runtime in any number of different ways that may make sense for a given problem.

For example, as I was working on #8954 I wanted to:

• Invoke an arbitrary function within an arbitrary wat/wasm file and a specified VM (or multiple of them), see the output, etc.;
• View the input wasm and wat;
• View the prepared wasm and wat at every step of the preparation pipeline;
• View the assembly code for a given wasm contract and/or function;
  • For VMs that have other IRs, ability to output those IRs would be dope;
• Run the contract with a instruction-count-precise profiler or a debugger;
  • even better there's somehow some proper debuginfo that these tools can discover e.g. functions, locals, etc;
  • failing that, output information that would allow manually cross-correlating;
  • instruction heatmaps, ability to straightforwardly emulate a execution of a given function, etc...
• Reproducible memory offsets (no ASLR), especially for the VM mmaps.

In the future we may want to add commands that would allow to exercise e.g. the various contract caches, host functions, etc. as well, especially outside of WASM contract context.

---

This should be a tool that's easy to extend as future use-cases come up.

[stale]

This issue has been automatically marked as stale because it has not had recent activity in the last 2 months.
It will be closed in 7 days if no further activity occurs.
Thank you for your contributions.

[nagisa]

Superseded by #12755.