Actions
Bug #7338
closedrust: different int types turn garbage on FFI boundary
Affected Versions:
Effort:
Difficulty:
Label:
Description
For example, in output-json-anomaly.c we have:
int r;
r = AppLayerGetEventInfoById(event_code, &event_name, &event_type);
Ultimately, at least for
bittorrent-dht this results in a Rust function being called where the return type is i8. Even though Rust appears to return 0, the value seen by C is garbage.
- Likely due to the update to LLVM 19 in Rust 1.82.0.
- Doesn't appear to affect release builds, only debug builds.
- Only seems to affect return values, not return by argument style pointers.
Actions