|An Introduction to GCC - for the GNU compilers gcc and g++|
by Brian J. Gough, foreword by Richard M. Stallman
Paperback (6"x9"), 144 pages
RRP £12.95 ($19.95)
"A wonderfully thorough guide... well-written, seriously usable information" --- Linux User and Developer Magazine (Issue 40, June 2004) Get a printed copy>>>
13.4 Runtime error messages
error while loading shared libraries:
cannot open shared object file: No such file or directory
The program uses shared libraries, but the necessary shared library
files cannot be found by the dynamic linker when the program starts.
The search path for shared libraries is controlled by the environment
LD_LIBRARY_PATH(see section 3.2 Shared libraries and static libraries).
These runtime messages indicate a memory access error.
Common causes include:
- dereferencing a null pointer or uninitialized pointer
- out-of-bounds array access
- incorrect use of
freeand related functions
- use of
scanfwith invalid arguments
floating point exception
This runtime error is caused by an arithmetic exception, such as
division by zero, overflow, underflow or an invalid operation (e.g.
taking the square root of -1). The operating system determines
which conditions produce this error. On GNU systems, the functions
fedisableexceptcan be used to trap or mask each type of exception.
- This error is produced by the operating system when an illegal machine instruction is encountered. It occurs when code has been compiled for one specific architecture and run on another.
|ISBN 0954161793||An Introduction to GCC - for the GNU compilers gcc and g++||See the print edition|