I am not sure about what you want to achieve but maybe 'svmon' is the command you are looking for. E.g. use
Code:
svmon -P <yourpid>
to see how much memory a process uses, how much memory of it is pinned and how much memory is in paging space, how big shared library segments are and so on. Have a look at the svmon man page.
Hello everybody,
I am having major problems at the moment with shared libraries and I have to little knowledge of them to solve them. So please, please help me :)
Ok this is the problem:
I have a library A, which uses B and C, and C uses again D.
If I try to run A as plugin in apache,... (0 Replies)
How do i make a library shared
say i have a library a.so which i have just compiled.
I want to make it shared how do i make it
Next Queation is what is the difference between a.so.0 a.so.1 a.so.2 & a.so :rolleyes: (1 Reply)
Hi everybody!
I would like to set in the makefile a path that should be the path where the program searches for the libraries loaded at run time.
Is there such a variable to be set in makefile?
Thanks in advance! (1 Reply)
can someone explain whether my understanding is correct
lets suppose we have a program that uses library x.
if x is static then the code of x will be part of our program, so if we're going to have 5 executables of our program, then each executable will have x as part of it.
Also, x does not... (2 Replies)
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)
Hello guys, I have a trouble when running an application in AIX, I've compiled and the
LIBRARY_PATH seems ok, but I get the following message:
rtld: 0712-001 Symbol __pthread was referenced
from module main_app(), but a runtime definition
of the symbol was not found
ldd... (4 Replies)
Each shared library may contain sections with allocatable flag as below:
...
.hash
.gnu.hash
.dynsym
.dynstr
.gnu.version
.gnu.version_d
.rel.dyn
.rel.plt
.plt
...
My questions is that: among above sections, which of them should be loaded in the physical memory by run-time linker... (3 Replies)
Discussion started by: Dongping84
3 Replies
LEARN ABOUT NETBSD
shmdt
SHMAT(2) BSD System Calls Manual SHMAT(2)NAME
shmat, shmdt -- map/unmap shared memory
LIBRARY
Standard C Library (libc, -lc)
SYNOPSIS
#include <sys/shm.h>
void *
shmat(int shmid, const void *shmaddr, int shmflg);
int
shmdt(const void *shmaddr);
DESCRIPTION
shmat() maps the shared memory segment associated with the shared memory identifier shmid into the address space of the calling process. The
address at which the segment is mapped is determined by the shmaddr parameter. If it is equal to 0, the system will pick an address itself.
Otherwise, an attempt is made to map the shared memory segment at the address shmaddr specifies. If SHM_RND is set in shmflg, the system
will round the address down to a multiple of SHMLBA bytes (SHMLBA is defined in <sys/shm.h>).
A shared memory segment can be mapped read-only by specifying the SHM_RDONLY flag in shmflg.
shmdt() unmaps the shared memory segment that is currently mapped at shmaddr from the calling process' address space. shmaddr must be a
value returned by a prior shmat() call. A shared memory segment will remain in existence until it is removed by a call to shmctl(2) with the
IPC_RMID command.
RETURN VALUES
shmat() returns the address at which the shared memory segment has been mapped into the calling process' address space when successful,
shmdt() returns 0 on successful completion. Otherwise, a value of -1 is returned, and the global variable errno is set to indicate the
error.
ERRORS
shmat() will fail if:
[EACCES] The calling process has no permission to access this shared memory segment.
[ENOMEM] There is not enough available data space for the calling process to map the shared memory segment.
[EINVAL] shmid is not a valid shared memory identifier.
shmaddr specifies an illegal address.
[EMFILE] The number of shared memory segments has reached the system-wide limit.
shmdt() will fail if:
[EINVAL] shmaddr is not the start address of a mapped shared memory segment.
SEE ALSO ipcrm(1), ipcs(1), mmap(2), shmctl(2), shmget(2)STANDARDS
The shmat and shmdt system calls conform to X/Open System Interfaces and Headers Issue 5 (``XSH5'').
HISTORY
Shared memory segments appeared in the first release of AT&T System V UNIX.
BSD June 17, 2002 BSD