Add support for step debugging and Virtual Machine introspection

[huhlig]

It would be desirable to be able to execute wasm instruction by instruction and expose the machine's internal instance memory space read only for debugging purposes as well as time sharing. Creation of a debug context containing the textualized Source code and a pointer to the current instruction would help as well.

[lachlansneff]

Yes! I completely agree. We definitely want to supply the ability to debug your code running within the wasmer runtime. We will update this issue as we start working on it.

[void4]

Being able to serialize the virtual machine runtime state in external calls (not only the memory after the call to the wasm binary has terminated, but when wasm calls into the environment again) would be amazing. https://github.com/perlin-network/life supports this

[stale[bot]]

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

[stale[bot]]

Feel free to reopen the issue if it has been closed by mistake.

[huhlig]

Wow this was completed! Do you guys have the docs for it?

[bjorn3]

I don't think it is done. The stale bot closed it due to no recent activity. These bots do more harm than good IMO as they don't have the necessary context. All they do is make it seem like there are less issues than there really are.

[huhlig]

Ahh I was confused that it was moved to Done rather than the Icebox.

[syrusakbary]

Not sure why it was marked as done, apologizes for that. @Hywan perhaps we need to update the stale bot? Or put a bigger window of time for closing stale tickets?

[Hywan]

We should have noticed the message from the bot and removed the stale label. It's a tool we are experiencing for the moment, but so far I'm happy with it. The issue is now re-opened, everything is fine :-).

[kaimast]

@Hywan is there a branch we can test this on?

[syrusakbary]

Revisit for milestone 2.x