wasm-trace

wasm-trace copied to clipboard

Currently we only support logging `i32` return values (although the epilogue instrumentation code already allocates a local with the correct size). We should change this to handle all four wasm...

sliminality

Ideas from Nick: - For a series of captured stacks: a call tree with counts (can be inverted too). For example, trace the stack whenever we call the free function,...

sliminality

Allow users to specify a regex or pattern, and only instrument functions matching that regex.

sliminality

Along the lines of #13, users should be able to pass in a `--buffer-size` argument to specify the number of bytes to hold in the ring buffer.

sliminality

See discussion in #7. We should get rid of the `tracer_dependencies!` and `tracer_bootstrap!` macros, and initialize everything in `lib.rs`.

sliminality

The current example program in the README (`function-calls`) is rather long. We should come up with a more succinct example.

sliminality