I think it’s fine for now. AFAIK both result codes are only used by Intel's kAFL fork (though the fork doesn't use libnyx yet). But yeah...we should definitely extend NxyReturnValue in the future.
Anyway, thanks again for your PR :)

@schumilo actually I got the "starved" result code from QEMU-Nyx, which crashed the fuzzer 😅 . It was recently merged into the main branch from qemu-nyx-4.2.0-dev-intel (nyx-fuzz/QEMU-Nyx#10).

@acidghost the starved result code should only trigger if you provide non-zero argument in the RELEASE hypercall. Did you observe something different?

nyx-fuzz/QEMU-Nyx@c12c6bd#diff-1872baa30d6294198890713430742623fe37ffe1912e9df79c9b76a9746eb1d6

@schumilo I guess this bit is another candidate for the generic ijon/aux return info buffer

@il-steffen I'm aware of that, but I can trigger the crash reliably on LightFTP (see nyx-fuzz/packer#10) 🤷