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
We could use the trace log to generate analysis tests for Rizin.
The analysis test could be of the form:
aezi
aezsu <address>
# check register content
# Execute until some other address and test regs.
...
rz-tracetest could just emit these execute until address X and test reg contenti times.
This would give us semantic tests in Rizin. Also for binaries with enormous traces (500MB and way more). Without the overhead of running rz-tracetest in the CI.
The text was updated successfully, but these errors were encountered:
We could use the trace log to generate analysis tests for Rizin.
The analysis test could be of the form:
rz-tracetest could just emit these
execute until address X and test reg content
i
times.This would give us semantic tests in Rizin. Also for binaries with enormous traces (500MB and way more). Without the overhead of running rz-tracetest in the CI.
The text was updated successfully, but these errors were encountered: