errno 84 (ELIBBAD): meaning and diagnosis

Status / error code:		Category:

Constant name:
Source:		Operating System:
Description: Accessing a corrupted shared lib.

Could be also:
Constant	Type	OS
ERROR_OUT_OF_STRUCTURES	Win32 error	Windows
EILSEQ	errno	Linux
EOVERFLOW	errno	Mac
LM_SERVER_INTERNAL_ERROR	BugCheck Code	Windows

Previous	Next
ELIBACC	ELIBSCN

ELIBBAD

The library was required but could not be loaded

Solaris associates ELIBBAD with old a.out execution and static shared libraries. The executable requires a library to be linked in during exec, but the loader cannot load that library; Oracle says the library is probably corrupted.

This narrows the failure beyond the constant's short text. A missing or inaccessible library maps to ELIBACC, while erroneous .lib metadata in the executable has its own ELIBSCN code. ELIBBAD focuses on the loadability of the required library artifact.

What to preserve when analyzing an old executable

Record the executable format and the exact required static shared-library file selected by the old loader.
Compare the library with a known-good copy and inspect truncation or on-disk corruption before changing search paths.
Do not automatically translate this obsolete errno to a current ELF dynamic-linker error; the historical format and loader contract are part of the diagnosis.

References

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