06-03-2005
dynamically loaded libraries
how to get the list of all dynamically loaded libraries in memory ?thanks!
10 More Discussions You Might Find Interesting
1. HP-UX
HI,
I am dynamically loading shared libraries using shl_load(). There are multiple processes (50 or more) which loads the same shared library. Will Unix internally load only one copy of the shared library or it will load multiple copies.
Can I have memory issues if this is done.
Thanks,... (1 Reply)
Discussion started by: Debasisb2002
1 Replies
2. UNIX for Dummies Questions & Answers
Hello everyone. I am new to these forums and also new to Unix. And by saying "new to Unix" I mean I have never used it and 10 minutes ago was asked to start learning. So here I am.
I was wondering if anyone could help me find out how long it would take to write code in Unix that will do the... (1 Reply)
Discussion started by: idesaj
1 Replies
3. Programming
hi all,
i have a critical and specific problem with respect to set uid bit on user and the dll's
for a binary, (under the userid A)
it needs libraries from /usr/lib and informix libraries from $INFORMIXDIR/lib/esql
but this binary should be kicked off from id B,
hence s-bit on user is... (5 Replies)
Discussion started by: matrixmadhan
5 Replies
4. Programming
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)
Discussion started by: nadiamihu
1 Replies
5. Programming
anybody knows how to view loaded shared libraries by running processes in linux enviornment? any command or tool ?
thanks a lot (3 Replies)
Discussion started by: princelinux
3 Replies
6. UNIX for Advanced & Expert Users
I am trying to install a scientific program onto my mac and when i try and execute it this error comes up and i cant find any literature on the net to fix it...
dyld: Library not loaded: /usr/local/lib/libgfortran.2.dylib
Referenced from:... (4 Replies)
Discussion started by: olifu02
4 Replies
7. AIX
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)
Discussion started by: edgarvm
4 Replies
8. AIX
Hi,
I have a problem about loaded shared libraries. I'm issuing ‘procldd' for a process and AIX shows me the loaded shared libraries. I'm collecting these libraries and counting their size. They were 350MB. After this, I'm issuing ‘ps vx' and I'm seeing that the process takes 130MB from AIX's... (1 Reply)
Discussion started by: jhatzics
1 Replies
9. BSD
Heyas
Since freebsd has set TERM to xterm when in terminal mode, i'm very curious what its value will be in GUI mode - seems its xterm (in x11/twm) as well.. how smart :eek: :(
So i've installed: awesome and xorg, but when calling awesome, it talks something about invalid display.
So i've... (1 Reply)
Discussion started by: sea
1 Replies
10. UNIX for Advanced & Expert Users
hi,
would like to know if anyone knows or could verify and give me an answer on when autosys does actually load the profile whether in Activated state or Running state.
Scenerio am trying to look for is
Lets say i have a profile variable DATE=Mar052015
Start jobA --> JobB depends on A -->... (0 Replies)
Discussion started by: veshwar
0 Replies
LEARN ABOUT DEBIAN
ne_sock_exit
NE_SOCK_INIT(3) neon API reference NE_SOCK_INIT(3)
NAME
ne_sock_init, ne_sock_exit - perform library initialization
SYNOPSIS
#include <ne_socket.h>
int ne_sock_init(void);
void ne_sock_exit(void);
DESCRIPTION
In some platforms and configurations, neon may be using some socket or SSL libraries which require global initialization before use. To
perform this initialization, the ne_sock_init function must be called before any other library functions are used.
Once all use of neon is complete, ne_sock_exit can be called to perform de-initialization of socket or SSL libraries, if necessary. Uses of
ne_sock_init and ne_sock_exit are "reference counted"; if N calls to ne_sock_init are made, only the Nth call to ne_sock_exit will have
effect.
ne_sock_init will set the disposition of the SIGPIPE signal to ignored. No change is made to the SIGPIPE disposition by ne_sock_exit.
Both the SSL libraries supported by neon -- OpenSSL and GnuTLS -- require callbacks to be registered to allow thread-safe use of SSL. These
callbacks are stored as global variables and so their state persists for as long as the library in question is loaded into the process. If
multiple users of the SSL library exist within the process, this can be problematic, particularly if one is dynamically loaded (and may
subsequently be unloaded).
If neon is configured using the --enable-threadsafe-ssl flag, thread-safe SSL support will be enabled automatically, as covered in the
following section. Otherwise, it is not safe to use neon with SSL in a multi-threaded process. The ne_has_support function can be used to
determine whether neon is built to enable thread-safety support in the SSL library.
Thread-safe SSL with OpenSSL
neon follows two simple rules when dealing with the OpenSSL locking callbacks:
o ne_sock_init will set thread-safety locking callbacks if and only if no locking callbacks are already registered.
o ne_sock_exit will unset the thread-safety locking callbacks if and only if the locking callbacks registered are those registered by
ne_sock_init.
Applications and libraries should be able to co-operate to ensure that SSL use is always thread-safe if similar rules are always followed.
Thread-safe SSL with GnuTLS
The cryptography library used by GnuTLS, libgcrypt, only supports an initialization operation to register thread-safety callbacks.
ne_sock_init will register the thread-safe locking callbacks on first use; ne_sock_exit cannot unregister them. If multiple users of GnuTLS
are present within the process, it is unsafe to dynamically unload neon from the process if neon is configured with thread-safe SSL support
enabled (since the callbacks would be left pointing at unmapped memory once neon is unloaded).
RETURN VALUE
ne_sock_init returns zero on success, or non-zero on error. If an error occurs, no further use of the neon library should be attempted.
SEE ALSO
neon(3), ne_has_support(3)
AUTHOR
Joe Orton <neon@lists.manyfish.co.uk>
Author.
COPYRIGHT
neon 0.29.6 3 May 2011 NE_SOCK_INIT(3)