a tool that would take a wasm module and modify its code to inject tracing calls, so that you could get an trace of the wasm's execution in the console
Based on an idea by Nick Fitzgerald from Mozilla.
Given the following Rust program:
#[macro_use]
extern crate wasm_trace;
use wasm_trace::tracer::Tracer;
tracer_dependencies!();
tracer_bootstrap!();
#[no_mangle]
pub extern "C" fn do_stuff(x: i32) -> i32 {
println!("{}", double(x) + double(x));
println!("{}", factorial(x as u32));
let result = double(x) + negate(5) + 1;
void();
return result;
}
#[no_mangle]
pub fn double(x: i32) -> i32 {
return x * 2;
}
#[no_mangle]
pub fn negate(x: i32) -> i32 {
return -1 * x;
}
#[no_mangle]
pub fn void() {
println!("No return value here!");
}
#[no_mangle]
pub fn factorial(n: u32) -> u32 {
if n == 1 || n == 0 {
1
} else {
n * factorial(n - 1)
}
}We can compile this program to a .wasm binary and pass that binary to our program:
> cargo build --example function-calls --target=wasm32-unknown-unknown
> cp target/wasm32-unknown-unknown/debug/examples/function-calls.wasm .
> cargo run function-calls.wasm # `cargo run` our `wasm-trace` binaryThis will output an instrumented binary called output.wasm. We can evaluate this module in Node.js and invoke do_stuff(4):
> node examples/js/runWasm.js function-calls.wasm do_stuff 4
Invoking exported function do_stuff with arguments [ 4 ] ...
Result of function call: 4
call function do_stuff
| call function double
| return 8 from double
| call function double
| return 8 from double
| call function factorial
| | call function factorial
| | | call function factorial
| | | | call function factorial
| | | | return 1 from factorial
| | | return 2 from factorial
| | return 6 from factorial
| return 24 from factorial
| call function double
| return 8 from double
| call function negate
| return -5 from negate
| call function void
| return from void
return 4 from do_stuffYou can preview the changes to the disassembly.
Install the WebAssembly toolchain:
rustup update
rustup target add wasm32-unknown-unknown --toolchain nightlyIn addition, the following binaries must be installed to run the tests in tests/:
- wasm-gc, which removes unneeded exports, imports, and functions.
- Binaryen, a compiler
toolchain for WebAssembly. In particular, we're using the
wasm-distool to disassemble a.wasmbinary into the readable.watS-expression format. - Node.js with WebAssembly support.
Meg Grasse and Sarah Lim, with support from Jim Blandy and Nick Fitzgerald.