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
When showing dependencies, bpfvv now correctly identifies instructions with "side-effect" changes. That is, when the verifier prints an updated value for a slot that is not directly affected by the instruction.
If you load this into bpfvv, and click on r6 at instruction 120, the app correctly detects side-effects changing r6:
at 60: ptr_node_data(ref_obj_id=2) -> ptr_node_data(non_own_ref)
at 99: ptr_node_data(non_own_ref) -> scalar()
Because of that instructions 60 and 99 are highlighted. However, in order to see how r6 changed there, one has to click on the line to and see the change in the state panel:
output.mp4
The task is to detect this situation, and modify dependency lines such that tracked value-change is shown. For example, we could show:
When showing dependencies, bpfvv now correctly identifies instructions with "side-effect" changes. That is, when the verifier prints an updated value for a slot that is not directly affected by the instruction.
Example (extracted from this log):
If you load this into bpfvv, and click on
r6at instruction 120, the app correctly detects side-effects changingr6:ptr_node_data(ref_obj_id=2)->ptr_node_data(non_own_ref)ptr_node_data(non_own_ref)->scalar()Because of that instructions 60 and 99 are highlighted. However, in order to see how
r6changed there, one has to click on the line to and see the change in the state panel:output.mp4
The task is to detect this situation, and modify dependency lines such that tracked value-change is shown. For example, we could show:
Or
with
r6being interactive