No documentation for how to run on an individual Wasm module

[samestep]

From the paper:

the diverse host environments and engine offerings for Wasm demand a more general technique that works with an uncooperative host environment. The term “uncooperative” here means that the host environment does not provide any support for record and replay. Instead, Wasm-R3 works without any modifications of the host environment or the underlying Wasm engine, but instruments a Wasm module so that it records its own trace.

It sounds like this project can take in a *.wasm module and spit out a modified *.wasm module that records a trace. However, in this repo's README.md, I don't see any documentation on how to do that, nor on how specifically to use such the modified Wasm module once it has been created.

I tried the npm start example in the README, but it asks me to run npx playwright install to "download new browsers", which I don't think I should need to do for my use case: I just want to use Wasm-R3 to debug a Wasm module I'm using in Node.js, not in a browser context.

Could you please add documentation on how to use Wasm-R3 on an individual Wasm module?

[doehyunbaek]

TLDR: Think the current implementation won't be much helpful. But curious of your use case summed up in a repo.

Hi!

It sounds like this project can take in a *.wasm module and spit out a modified *.wasm module that records a trace.

What we meant to say in the paper is that it can work even on uncooperative host environments, not without host environments. That is, individual *.wasm should run inside some kind of host environment (web engines / non-web engines), for Wasm-R3 to work. Or in general, I am not aware of running individual wasm module without any host envionment, can you elucidate me if you know other use cases?

which I don't think I should need to do for my use case: I just want to use Wasm-R3 to debug a Wasm module I'm using in Node.js, not in a browser context.

The current implementation does not implement recording of wasm module inside node.js. This repo contains only the implementation of wasm-r3 approach for the web host environment, and wizard project contain engine-level support of wasm-r3 approach, both for record and replay.

I think what wizard does is probably closer to what you want (input a *.wasm module, output a replay module), but as you mentioned that you are using node.js, probably it wouldn't be much help.

In addition, there is a very much ongoing work that uses a concept called selective record and replay to get an *.wasm module as an input and output reduced module, but it's not so polished for general use. If you want to explore, there is a open-source code and short talk describing the approach.

To sum up, I suspect the current implementation won't be much help to your suggestion. But if you are able to tidy up your use case into a single repo, I can take a look if there is a good workaround or whatnot. Regardless, I wholeheartedly agree that documentation has a room for improvement.