12-17-2007
Quote:
Originally Posted by
porter
That looks like a problem with dynamic loading.
1.Have you built all shared libraries?
not sure i can ask
2. Are any of the shared libraries implemented in C++?
ditto
3. Did you use the same compiler on *all* modules, shared and application? no
4. Have you tried "ldd"? Can this resolve all modules?
not sure can ask
5. Please post "uname -a" of system. Is this 32 bit/64 bit, PA-RISC or Itanium?
uname -a
HP-UX hpuxpit0 B.11.11 U 9000/800 3003499885 unlimited-user license
Another feature of HPUX is that unless you are careful the build process won't warn you of unresolved dependencies.
uname -a
HP-UX hpuxpit0 B.11.11 U 9000/800 3003499885 unlimited-user license
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
We build our code on all platforms Sol, Hp, Aix, Sgi & linux.
Some base libraries have changed.
All the dependent exe & lib which use those base libraries have changed in all platforms in terms of size/checksum or both except linux.
No code has changed in these.
We have a post utility... (8 Replies)
Discussion started by: vibhor_agarwali
8 Replies
2. UNIX for Advanced & Expert Users
Hi All,
I have a problem with the shared objects setup in AIX. We have a customized shell written by the developers over here. When i issue a MQ Series command (mqsilist) it is giving the error as . All the commands making use of this libImbCmdLib.a.so is failing. But when executed in normal... (1 Reply)
Discussion started by: dhanamurthy
1 Replies
3. AIX
Hi friends..
Help to solve this issue...
Is there any parameter setting to control or limit the size of the shared memory a process can attach for the below specified environment?
The man pages says it can attach upto segments of size 2GB. But when our process (which also connects to... (0 Replies)
Discussion started by: sdspawankumar
0 Replies
4. HP-UX
I have never seen this issue before, but here is what is happening. I link an executable against two dynamic mlib libraries veclib and lapack. We place a newer version of these libraries in a write only directory and point the shlib_path at that directory. When the executable runs, it gets a... (3 Replies)
Discussion started by: sambarusty
3 Replies
5. Red Hat
Hello,
I'm experimenting a problem on my rh server.
Red Hat Enterprise Linux AS release 3 (Taroon Update 8)
2.4.21-47.ELsmp #1 SMP i686 i686 i386 GNU/Linux
It started with a segmentation fault on
#id root
To resolve it, I've installed
coreutils-4.5.3-28.4.i386.rpm
But, I... (6 Replies)
Discussion started by: gogol_bordello
6 Replies
6. Programming
for example, I have a static lib name liba.a
it offers some interface such a1();a2();
but i do not have the source code of liba.a;
If i would like to create a shared object, and offer the similar interface of
a1 and a2;
Is there a way to fulfill such requirement?
thanks. (7 Replies)
Discussion started by: flost
7 Replies
7. AIX
Hi all,
I am developing an application with two components. One "c" binary and one "C++" shared object.
While execution, the shared object crashes out and core dump is created whenever "new" is executed. But if i use malloc this will work perfectly.
I tried to use dbx. Below given was... (1 Reply)
Discussion started by: itssujith
1 Replies
8. Linux
Hi,
I have 2 linux servers. One of them has a mount which I have mapped to a shared samba directory on the other server. Below will help you understand better.
smb.conf on Server1:
workgroup = WRKGRP
netbios name = smbserver
security = SHARE
load printers = No
default service = global... (11 Replies)
Discussion started by: satishrao
11 Replies
9. Shell Programming and Scripting
I have a C++ binary executable installed in a file system which is shared across multiple solaris boxes.
When I start this executable from one of the boxes,I am able to start only 4 parallel instances and from the 5th instance onwards I am getting the following error.
fatal: libdb2.so.1:... (2 Replies)
Discussion started by: prasperl
2 Replies
10. Programming
Hello.
I am new to this forum and I would like to ask for advice about low level POSIX programming.
I have to implement a POSIX compliant C shared library.
A file will have some variables and the shared library will have some functions which need those variables.
There is one special... (5 Replies)
Discussion started by: iamjag
5 Replies
LDD(1) Linux Programmer's Manual LDD(1)
NAME
ldd - print shared object dependencies
SYNOPSIS
ldd [option]... file...
DESCRIPTION
ldd prints the shared objects (shared libraries) required by each program or shared object specified on the command line. An example of
its use and output is the following:
$ ldd /bin/ls
linux-vdso.so.1 (0x00007ffcc3563000)
libselinux.so.1 => /lib64/libselinux.so.1 (0x00007f87e5459000)
libcap.so.2 => /lib64/libcap.so.2 (0x00007f87e5254000)
libc.so.6 => /lib64/libc.so.6 (0x00007f87e4e92000)
libpcre.so.1 => /lib64/libpcre.so.1 (0x00007f87e4c22000)
libdl.so.2 => /lib64/libdl.so.2 (0x00007f87e4a1e000)
/lib64/ld-linux-x86-64.so.2 (0x00005574bf12e000)
libattr.so.1 => /lib64/libattr.so.1 (0x00007f87e4817000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f87e45fa000)
In the usual case, ldd invokes the standard dynamic linker (see ld.so(8)) with the LD_TRACE_LOADED_OBJECTS environment variable set to 1.
This causes the dynamic linker to inspect the program's dynamic dependencies, and find (according to the rules described in ld.so(8)) and
load the objects that satisfy those dependencies. For each dependency, ldd displays the location of the matching object and the (hexadeci-
mal) address at which it is loaded. (The linux-vdso and ld-linux shared dependencies are special; see vdso(7) and ld.so(8).)
Security
Be aware that in some circumstances (e.g., where the program specifies an ELF interpreter other than ld-linux.so), some versions of ldd may
attempt to obtain the dependency information by attempting to directly execute the program, which may lead to the execution of whatever
code is defined in the program's ELF interpreter, and perhaps to execution of the program itself. (In glibc versions before 2.27, the
upstream ldd implementation did this for example, although most distributions provided a modified version that did not.)
Thus, you should never employ ldd on an untrusted executable, since this may result in the execution of arbitrary code. A safer alterna-
tive when dealing with untrusted executables is:
$ objdump -p /path/to/program | grep NEEDED
Note, however, that this alternative shows only the direct dependencies of the executable, while ldd shows the entire dependency tree of
the executable.
OPTIONS
--version
Print the version number of ldd.
-v, --verbose
Print all information, including, for example, symbol versioning information.
-u, --unused
Print unused direct dependencies. (Since glibc 2.3.4.)
-d, --data-relocs
Perform relocations and report any missing objects (ELF only).
-r, --function-relocs
Perform relocations for both data objects and functions, and report any missing objects or functions (ELF only).
--help Usage information.
BUGS
ldd does not work on a.out shared libraries.
ldd does not work with some extremely old a.out programs which were built before ldd support was added to the compiler releases. If you
use ldd on one of these programs, the program will attempt to run with argc = 0 and the results will be unpredictable.
SEE ALSO
pldd(1), sprof(1), ld.so(8), ldconfig(8)
COLOPHON
This page is part of release 4.15 of the Linux man-pages project. A description of the project, information about reporting bugs, and the
latest version of this page, can be found at https://www.kernel.org/doc/man-pages/.
2017-09-15 LDD(1)