paritytech/wasm-instrument

Issues

• Potenitally incorrect frame border check in pop_values

  #86 opened 8 months ago by Harrm
  4

• get rid of confusing `ACTIVATION_FRAME_COST` constant

  #80 opened 10 months ago by StackOverflowExcept1on
  5

• thunk calls might be instrumented incorrectly

  #82 opened 10 months ago by StackOverflowExcept1on
  0

• How to get the remaining gas once execution has ran out of gas?

  #39 opened a year ago by ok-ul-ch
  2

• Userspace gas metering

  #11 opened 2 years ago by athei
  1

• Switch to `wasmparser` and `wasm-encoder`

  #3 opened 3 years ago by athei
  2

• Release 0.1.2 as 0.2.0

  #20 opened 2 years ago by bkchr
  1

• Update debug information when injecting gas metering

  #15 opened 2 years ago by mangas
  4

• Expose more features from parity-wasm

  #4 opened 3 years ago by nazar-pc
  3

• Stack depth instrumentation fails to account for the full function activation stack frame

  #1 opened 3 years ago by nagisa
  5