| Previous | Next |
| KERN_RPC_SERVER_TERMINATED | KERN_RPC_CONTINUE_ORPHAN |
KERN_RPC_TERMINATE_ORPHAN
A legacy Mach RPC control outcome
KERN_RPC_TERMINATE_ORPHAN is not a normal application-level failure. XNU labels it as an instruction to terminate an orphaned activation, placing it in the internal control flow of legacy Mach RPC and thread-activation handling.
If this value appears in low-level diagnostics, keep it separate from the request business result. The actionable question is why the RPC execution context became orphaned: for example, whether the peer, task, or owning service disappeared before the normal completion path.
What to inspect
- Record the RPC endpoint, task/thread lifecycle events, and preceding IPC status.
- Look for a service exit or teardown that races an outstanding request.
- Do not expose this code to callers as proof that their requested operation was rejected on semantic grounds.
- Prefer a supported higher-level service API where available rather than relying on legacy Mach activation behavior.
References
- Apple XNU: kern_return.h
- Apple Kernel Programming Guide: Mach IPC and MIG
- Apple Developer Documentation: Mach interface collection
Looking for a different code? Search another status or error code.