wasm-edit 0.1.5

Edit and instrument already compiled Wasm binaries
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50

# wasm-edit

> Edit and instrument already compiled Wasm binaries

## Install

```
cargo install wasm-edit
```

## Edit the main memory

Change the initial memory amount (in pages):
```
wasm-edit edit-memory --initial-memory=1000 < input.wasm > output.wasm
```

## Trace calls to `memory.grow`

Trace calls to the `memory.grow` instruction:
```
wasm-edit instrument-memory < input.wasm > output.wasm
```

Requires Wasi, but doesn't require any change on the host.
Tested with Rust and theoretically working with C/C++ (clang).

## Coredump generation

Add the coredump generation:

```
wasm-edit coredump < input.wasm > output.wasm
```

When WebAssembly encounters a `unreachable` instruction it will unwind
the stack, collect informations and generate a coredump.

The coredump struct is stored at a fixed location, this might conflict with other transformations like asyncify.

Collect the entire WebAssembly memory and use [wasmgdb] to analyze.

## Running into stack overflow

Some Wasm binaries have very recursive flow of control, increase the maximum stack size:
```
$ ulimit -s 160000
```

[wasmgdb]: https://github.com/xtuc/wasmgdb