bpf2c needs better diagnostics support. #3879
Labels
blocked
Blocked on another issue that must be done first
enhancement
New feature or request
P2
triaged
Discussed in a triage meeting
Milestone
Describe the feature you'd like supported
When bpf2c fails to validate a command, the results are lackluster:
Verification failed for StringOpsTest with error error: mismatched EBPF_ARGUMENT_TYPE_PTR_TO* and EBPF_ARGUMENT_TYPE_CONST_SIZE_OR_ZERO: bpf_strchr
With no further explanation, including what arguments the verifier found, it's difficult to understand these failures without running bpf2c under a debugger directly and breaking on the exception that it throws.
Proposed solution
Adding a
--verbose
flag and extended logging to the running system.Additional context
There's a verbose option on the runtime verifier (
netsh ebpf sh ver ... level=verbose
) and the goal here would be to add similar behavior in the build step.The text was updated successfully, but these errors were encountered: