| Previous | Next |
| MACH_SEND_INVALID_CONTEXT | MACH_SEND_NO_GRANT_DEST |
MACH_SEND_INVALID_RT_OOL_SIZE
A compatibility constant, not a current recovery branch
MACH_SEND_INVALID_RT_OOL_SIZE is preserved in the public numeric namespace, but current XNU message.h explicitly labels it as a compatibility value that is no longer returned. Its name reflects older real-time message validation for out-of-line data; modern code should not expect a current mach_msg call to produce it.
This distinction is useful when reading old crash reports, imported telemetry, compatibility headers, or software that maps every historical constant to text. Observing the number in a contemporary process does not by itself prove that the current kernel rejected an out-of-line region for this historical reason. The value may have been serialized by an older component, copied from stale state, or generated by private compatibility code.
How to handle it
- Record the OS build, SDK/header version, and component that originated the status.
- Do not add an automatic resize-and-retry loop based solely on this constant.
- For current out-of-line failures, decode the actual active send error and any
MACH_MSG_VM_*supplemental bits. - Keep the symbolic mapping for log interpretation, while treating runtime occurrence as evidence requiring provenance.
References
Looking for a different code? Search another status or error code.