| Previous | Next |
| kOSMetaClassNoInsKModSet | kOSMetaClassInstNoSuper |
kOSMetaClassNoSuper
kOSMetaClassNoSuper denotes failure to associate a class with its superclass during OSMetaClass registration. The relationship is fundamental to the Libkern C++ runtime: it determines the class hierarchy used for type checks and object construction while a kext is being registered.
The current XNU source labels this branch as “never returned,” while retaining a log description for the historical condition. That makes the code useful chiefly when investigating old kernel-extension code or an XNU-derived implementation, not as a routine return from a modern application API.
How to interpret it
- Check that the intended superclass is linked, registered, and available before the derived class constructor runs.
- Review class-name spelling, load order, and any dependency that supplies the parent class.
- Use adjacent OSMetaClass logs to determine whether a prior registration error caused the missing association.
- Treat it as a loader/class-hierarchy defect rather than a device transport failure.
References
- Apple XNU: OSReturn.h
- Apple XNU: OSMetaClass.cpp
- Apple: deprecated kernel extensions and alternatives
Looking for a different code? Search another status or error code.