| Previous | Next |
| EILSEQ | ELIBBAD |
EOVERFLOW
The data may be valid, but the caller cannot represent it
EOVERFLOW is a representability failure. The filesystem, object, or kernel result may be valid, while the structure, integer type, time field, offset, identifier, or conversion target used by the caller is too narrow to hold it.
This differs from ERANGE, which is often associated with numeric conversion or mathematical results. For system interfaces, inspect ABI width, structure layout, large-file support, and the exact member that overflowed. Casting after the call cannot recover information that was rejected before a result could be delivered.
What to inspect
- Architecture, SDK, and the widths of
off_t, time, inode, UID/GID, and other result fields consumed by the caller. - The actual object size or identifier that triggered the failure, if a wider diagnostic path is available.
- Whether a legacy interface was selected instead of a newer API with an explicitly wide result type.
References
- Apple XNU: Darwin errno definitions
- POSIX: stat() and EOVERFLOW
- Apple system-call reference: EOVERFLOW
Looking for a different code? Search another status or error code.