09-02-2005
it depends on the size of the DSO, which you are linking
10 More Discussions You Might Find Interesting
1. Programming
I'm runtime linking (dlopen and dlsym) to a shared object (library) I've created and after a number of function calls into the library the program core dumps (Illegal operation). This only occurs during runtime linking. If I use the same library and dynamically link during compile time everything... (3 Replies)
Discussion started by: dneely
3 Replies
2. Programming
I asked the next question in a former thread :
Can I safely share objects that have virtual functions (i.e. have
virtual function table pointers) between two processes ?
Where will the pointers point to in each process ?
The objects are supposed to reside in shared memory
I received a... (6 Replies)
Discussion started by: Seeker
6 Replies
3. UNIX for Dummies Questions & Answers
Hi Friends !
I have a library, say libxyz.a.
To view all the object files in the archive, i issued the command :
ar -t libxyz.a
which displayed all the object files it contains.
Now, I would like to know the functions in each object file.
Is there any such command that displays... (3 Replies)
Discussion started by: mrgubbala
3 Replies
4. Programming
hi all !
Do I need all the shared objects to be present while compiling my code which has reference to a only one shared object, which in turn refers to another shared object.
for example I want to compile example.c which refers to sample.so
sample.so has refrence to anothersample.so
do... (2 Replies)
Discussion started by: disclaimer
2 Replies
5. UNIX for Advanced & Expert Users
Hi,
i am trying to debug a binary which is using a shared lib.
but i could not succeed in tracking the code flow in the classes defined
in this library.
i get: class MyClass <opaque> error
i followed the instructions in the link below:... (0 Replies)
Discussion started by: yakari
0 Replies
6. AIX
I have two envoirmets(Envoirment A and Envoirment B) running on same server(AIX vesion 5.3).Both have different groups.I am facing a strange problem.Shared objects of one envoirment (Envoirment A)are getting loaded into the second(Envoirment B).So the servers that have dependency on shared objects... (2 Replies)
Discussion started by: nitin@tcs
2 Replies
7. Programming
G'day,
I have been working with a large application that makes extensive use of templates. When compiled under Unix (with g++), this sees some rather impressive bloat. I have been trying to make a temporary quick-fix by using the -frepo option, which results in dramatically smaller shared... (0 Replies)
Discussion started by: Elric of Grans
0 Replies
8. Programming
Hi,
I am looking for references about creating and accessing Shared Objects (.so) through C/C++ on Unix / Linux platforms. Is it possible and where can I find the info.
Thanks
Phil (1 Reply)
Discussion started by: phil nascimento
1 Replies
9. Linux
dear Experts,
please help,
actually i am trying to create a .so(shared object through make file through ld)
i am not understaning how to proceed i have tried like
through command like i can do it in 2 step like
my progam :test2.c
$gcc -fPIC -c test2.c
$ld -shared -soname test2.so -o... (1 Reply)
Discussion started by: vin_pll
1 Replies
10. UNIX for Advanced & Expert Users
Hi All......
I have my tool in my one server lets say E1 and same tool I tried to install in E2 server so everything is fine but, while executing the my tool for example...
$ ./batch
At that time Im getting this following error.
./batch: error while loading shared libraries: libqabwvcd.so:... (3 Replies)
Discussion started by: ksrivani
3 Replies
plock(2) System Calls Manual plock(2)
NAME
plock() - lock process, text, data, stack, or shared library in memory
SYNOPSIS
DESCRIPTION
The system call allows the calling process to lock the text segment of the process (text lock), its data segment (data lock), or both its
text and data segment (process lock) into memory. Stack segments are also locked when data segments are locked. Shared library text and
shared library data segments (shlib lock) can also be locked. Locked segments are immune to all routine swapping. also allows these seg-
ments to be unlocked.
The effective user ID of the calling process must be a user with the privilege.
op must be one of the following:
Lock text and data segments into memory (process lock)
Lock text segment into memory (text lock)
Lock data segment into memory (data lock)
Remove locks
Lock shared library text and shared library data segments (shared library lock)
Lock text, data and shared library text and shared library data segments
into memory (process and shared library lock)
Lock text, shared library text and shared library data segments into memory
(text and shared library lock)
Lock data, shared library text and shared library data segments into memory
(data and shared library lock)
Although and the family of functions may be used together in an application, each may affect the other in unexpected ways. This
practice is not recommended.
Security Restrictions
Some or all of the actions associated with this system call require the privilege. Processes owned by the superuser have this privilege.
Processes owned by other users may have this privilege, depending on system configuration. See privileges(5) for more information about
privileged access on systems that support fine-grained privileges.
RETURN VALUE
returns the following values:
Successful completion.
Failure.
The requested operation is not performed. is set to indicate the error.
ERRORS
If fails, is set to one of the following values.
op is equal to and a process lock, a text lock, or a data lock already exists on the calling process.
op is equal to and a text lock or process lock already exists on the calling process.
op is equal to and a data lock, or process lock already exists on the calling process.
op is equal to and no type of lock exists on the calling process.
op is equal to and there are no unlocked shared library segments in the calling process.
op is equal to and a process lock, a text lock, or a data lock already exists on the calling process.
op is equal to and a text lock or process lock already exists on the calling process.
op is equal to and a data lock, or process lock already exists on the calling process.
op is not equal to one of the values specified in
is not allowed in a
window. See vfork(2).
There is not enough lockable memory in the system
to satisfy the locking request.
The effective user ID of the calling process
is not a user with the privilege.
EXAMPLES
The following call to locks the calling process in memory:
SEE ALSO
setprivgrp(1M), exec(2), exit(2), fork(2), getprivgrp(2), mlock(2), vfork(2), privileges(5).
STANDARDS CONFORMANCE
plock(2)