Re: looking for libc in wrong place

From: Rod Armstrong (rod_at_san-jose.tt.slb.com)
Date: Fri Feb 04 2000 - 18:22:06 GMT

• Next message: Laszlo Ladanyi: "linux binary"
• Previous message: J.W.Armstrong: "looking for libc in wrong place"
• In reply to: J.W.Armstrong: "looking for libc in wrong place"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]

James,
	The <bad text address> is beacuse of the load statement in your
~/.upsint file. The load and noload commands work like filters on the libraries
that ups reads. They do not affect the path that ups looks at to find
libraries. Implicitly, using load commands means that every other library
will not be loaded. It's usually better to use noload, because then 
everything else gets loaded. The sole purpose of the load/noload
commands is to speed up invocation time on large (>> 10 Meg) binaries.
	Try setting the environment variable VERBOSE before starting ups to 
see what libraries are being loaded. The list should be like that 
obtained by doing an ldd (or better, pldd if the OS supports it) on the
target. Your LD_LIBRARY_PATH may be wrong.

Rod

• Next message: Laszlo Ladanyi: "linux binary"
• Previous message: J.W.Armstrong: "looking for libc in wrong place"
• In reply to: J.W.Armstrong: "looking for libc in wrong place"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]

This archive was generated by hypermail 2.1.4 : Wed Feb 13 2002 - 21:51:33 GMT