Description
The function signatures returned by FuzzIntrospector's API differ from those in the YAML files provided by oss-fuzz-gen, causing issues when trying to use them together to extract API context information.
Example
1. bluez project - g_obex_new function
## conti-benchmark/comparison/bluez.yaml
return_type: "void"
signature: "GObex * g_obex_new(GIOChannel *, GObexTransportType, gssize, gssize)"
## FuzzIntrospector API response via query_fi_signature("bluez", "g_obex_new")
signature: "GObex *g_obex_new(GIOChannel *io, GObexTransportType transport_type, ...)"
Issues:
return_type field is "void" but signature shows "GObex *"
- Parameter names missing in YAML but present in FI API
Reproduction
# Query FI API via locally deployed FI:
curl "http://localhost:8080/api/function-signature?project=bluez&function=g_obex_new"
# Compare with YAML
grep -A 5 "g_obex_new" conti-benchmark/comparison/bluez.yaml
My question is: will oss-fuzz-gen correct the format of yaml file? Or will this be solved from the FI part?
Description
The function signatures returned by FuzzIntrospector's API differ from those in the YAML files provided by oss-fuzz-gen, causing issues when trying to use them together to extract API context information.
Example
1. bluez project -
g_obex_newfunctionIssues:
return_typefield is "void" but signature shows "GObex *"Reproduction
My question is: will oss-fuzz-gen correct the format of yaml file? Or will this be solved from the FI part?