What does errno 132 (EOVERFLOW) mean?

EOVERFLOW

EOVERFLOW is a UCRT POSIX compatibility constant for a result that cannot be represented in the destination type or result field required by an interface. It is not automatically a memory-allocation failure and it does not tell whether the source value is corrupt.

POSIX uses this condition for representability boundaries such as a file offset that does not fit in long or file metadata that cannot fit in the supplied structure. The diagnosis should therefore start with widths, signedness, conversion points, and the API variant used for the data size.

Useful checks

• Record the original value, destination type, bit width, signedness, and the conversion or API call that failed.
• Check whether a 64-bit-safe API, type, or data model is required for the intended input range.
• Do not silently truncate a size, offset, identifier, or count just to continue processing.

Microsoft lists EOVERFLOW in the UCRT POSIX supplement. For Windows-native calls, retain _doserrno or the API-specific error value alongside errno when the runtime provides one.

References

• POSIX: ftell()
• POSIX: fstat()
• Microsoft: errno and _doserrno

Looking for a different code? Search another status or error code.