You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The debugger should support in-browser fuzzing of multiple PVMs.
Depending on whether it's possible to use jazzer in browser (I believe not), we might need a backend that will be generating the programs.
After we get the program, we run that program on all PVMs the user have loaded (this may include uploaded WASM and most importantly external PVMs accessed via RPC) until there is a difference in registers/status/gas/pc.
If everything is okay, we move to another program. If not, we stop and let the user debug why it's wrong.
It should be possible to reset the execution of that program.
It should be possible to download the program for later use (generic format or SPI if we generate random registers as well).
This fuzzing will obviously not be very performant. The coverage will be take rather from typeberry implementation, not the implementation under test, yet I think it's still going to be extremely useful for anyone who wants to write PVM interpreter from scratch.
For more mature implementations it's definitely much better to have some native fuzzing solution instead.
The text was updated successfully, but these errors were encountered:
The debugger should support in-browser fuzzing of multiple PVMs.
jazzer
in browser (I believe not), we might need a backend that will be generating the programs.This fuzzing will obviously not be very performant. The coverage will be take rather from typeberry implementation, not the implementation under test, yet I think it's still going to be extremely useful for anyone who wants to write PVM interpreter from scratch.
For more mature implementations it's definitely much better to have some native fuzzing solution instead.
The text was updated successfully, but these errors were encountered: