Caesar Wang

> @ainhoa-a and @dtynn could you confirm if this would be useful to you? Yes. With the descriptor, we can check if the syscalls are compatible between different sdks automatically....

so basically speaking: 1. tracing & collecting profile data **from inside the wasm runtime** and make the data human-readable 2. find some way to enable the tracing only in dev...

hi @Stebalien would like to know if [wasm-coverage-demo](https://github.com/dtynn/wasm-coverage-demo) is helpful for this issue ?

completed a [simple demo](https://github.com/dtynn/ref-fvm/commit/b682aeb6326b4fbfaed52a055352ac2b0277680e), and captured a [coverage report](https://github.com/dtynn/ref-fvm/blob/8adc48a7eacc10748d166ee1733dc7bbd0be57fe/market_cover.out) for executing `test-vectors/corpus/extracted/0005-chocolate-01/fil_6_storagemarket/WithdrawBalance/Ok/ext-0005-fil_6_storagemarket-WithdrawBalance-Ok-1.json`.

> > Note: We probably don't need the human readable side of things. As long as the format is compatible with codecov. > sure, the reults could be the compatible...

Hi @mriise I did some work in #314, but as you know, it focus on generating & collecting coverage instruments inside **generated wasm bytecode**.. For this issue and its related...

ah, it would be nice to see some pieces of the work are useful to you., however, there are a few tricky steps before we can make everything work. let...

hi~ is [this](https://github.com/dtynn/ref-fvm/commit/00fe1e0673b7c8f415a6ee726564cfe7ae7cee56) ok for the issue? btw, is a `ActorID(0)` enough for the origin "system", or we should define it separately like ``` pub enum Originator { System, Actor(ActorID),...

then there would be a ``` pub strcut Originator { pub is_system: bool, pub actor_id: u64, } ``` or something like that in the `fvm_shared::sys` ?