Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Update disassembly output format for call arguments
* Display call arguments in the expected order and with the expected count * Make type display syntax consistent for pairs (which previously used " is ") vs singles (which previously used ":") * Put types before values so it looks more C like * Make type labels match between arguments, assertions, and preconditions (previously arguments showed "CTX" and "FD" for example whereas other places showed "ctx" and "map_fd") * Display "uint64_t" for types that can be anything, instead of an absent type, for consistency with how helper function prototypes are shown at https://github.com/iovisor/bpf-docs/blob/master/bpf_helpers.rst etc. This makes it clear to the viewer that the type is indeed known to not be ctx, map_fd, etc. (We could use "u64" instead but uint64_t is more of a standard.) Sample outputs: r0 = map_update_elem:2(map_fd r1, map_key r2, map_value r3, uint64_t r4) r0 = tail_call:12(ctx r1, map_fd r2, uint64_t r3) r0 = perf_event_output:25(ctx r1, map_fd r2, uint64_t r3, mem r4[r5?], uint64_t r5) r0 = skb_load_bytes:26(ctx r1, uint64_t r2, out r3[r4], uint64_t r4) r0 = sock_map_update:53(ctx r1, map_fd r2, map_key r3, uint64_t r4) Fixes vbpf#221 Signed-off-by: Dave Thaler <[email protected]>
- Loading branch information