08-11-2009
More information
I have tracked this issue to being something about memory locking over NFS. As soon as the process goes to mlockall, we update the modification time on the shared library. And if the shared library is read only, we get a Page I/O modification error. If I put the libraries local to the machine, it doesn't happen. So it seems to be some sort of NFS conflict. Has anyone seen this type of thing before?
---------- Post updated at 05:51 PM ---------- Previous update was at 06:35 AM ----------
found I was able to reproduce the symptom with just a hello world type of app.
#include <stdio.h>
#include <stdlib.h>
#include <sys/mman.h>
void main()
{
mlockall(CTL_CURRENT)
printf("hello world\n");
}
linked by the following
cc hello_world.c -o hello_world -L/opt/mlib/lib/pa2.0 -lveclib -llapack -Wl,s+
our home directories are NFS mounted so if I copy pa2.0 to /home/mine/pa2.0 and check the timestamp then
change my SHLIB_PATH EV to point to /home/mine/pa2.0
the timestamps change from the original copy after I run hello_world.
10 More Discussions You Might Find Interesting
1. Programming
hello all
I want to work in shared libraries how can i work in
Linux Environment ? (2 Replies)
Discussion started by: rajashekaran
2 Replies
2. UNIX for Advanced & Expert Users
What is the primary difference between static library and dynamic library?
and how to write static shared library? (1 Reply)
Discussion started by: areef4u
1 Replies
3. Programming
I need to create a shared library to access an in memory DB. The DB is not huge, but big enough to make it cumbersome to carry around in every single process using the shared library. Luckily, it is pretty static information, so I don't need to worry much about synchronizing the data between... (12 Replies)
Discussion started by: DreamWarrior
12 Replies
4. Programming
Is there any way in C to access a function in C shared library.
I have used dlopen to access /load the c shared library but unable to
use the function in the shared object.
Thanks in advance :b: (1 Reply)
Discussion started by: yhacks
1 Replies
5. Programming
I am writing a shared library in Linux (but compatible with other UNIXes) and I want to allow multiple instances to share a piece of memory -- 1 byte is enough. What's the "best" way to do this? I want to optimize for speed and portability.
Obviously, I'll have to worry about mutual exclusion. (0 Replies)
Discussion started by: otheus
0 Replies
6. Shell Programming and Scripting
Hi:
I have a library that it only offers Makefile for building static library. It built libxxx.a file. How do I in any way build a shared library? (either changin the Makefile or direct script or command to build shared library)
Thanks. (1 Reply)
Discussion started by: cpthk
1 Replies
7. UNIX for Dummies Questions & Answers
Hi,
I found a very strange thing when I linked my executable with a shared library. That is the executable only references a small function of the shared library, and the size of this function is only hundred bytes, but when I check the /proc/pid/smaps, I found that the 'Rss' of this shared... (8 Replies)
Discussion started by: Dongping84
8 Replies
8. OS X (Apple)
I'm trying to get Valgrind to work with an openmpi application in OS X. However I want to hardcode the path to a shared library called libmpiwrap-amd64-darwin.so into my application so that it is available at runtime. In Linux this is relatively simple, I would just add the option... (0 Replies)
Discussion started by: Valgrinder
0 Replies
9. 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
10. AIX
I'm trying to install libiconv to AIX 7.1 from an rpm off of the perzl site. The rpm appears to install but I get this error message.
add shr4.o shared members from /usr/lib/libiconv.a to /opt/freeware/lib/libiconv.a
add shr.o shared members from /usr/lib/libiconv.a to ... (5 Replies)
Discussion started by: kneemoe
5 Replies
LEARN ABOUT OPENDARWIN
cmpdylib
CMPDYLIB(1) General Commands Manual CMPDYLIB(1)
NAME
cmpdylib - compare two dynamic shared libraries for compatibility
SYNOPSIS
cmpdylib oldLibrary newLibrary
DESCRIPTION
cmpdylib compares two versions of a dynamic shared library to see if they are compatible with each other. If the two versions are incompat-
ible, the reason is printed to stdout, and the exit status is nonzero. If they are compatible, nothing is printed, and the exit status is
zero.
To see if the two versions are compatible, cmpdylib first verifies that newLibrary was built for all of the architectures that oldLibrary
was built for. If so, for each architecture, it checks to see if the global symbols defined in oldLibrary are still defined in newLibrary.
It then looks for new symbols, symbols defined in newLibrary that are not defined in oldLibrary. If it finds new symbols, it compares the
compatibility version numbers of the two libraries. If the compatibility version number of newLibrary is greater than oldLibrary, the
libraries are still compatible. If the compatibility version number is the same or less, the libraries are incompatible.
OPTIONS
oldLibrary
The older version of the library.
newLibrary
The newer version of the library.
EXAMPLES
This example shows the result of performing cmpdylib on two incompatible versions of the Foundation library. As stated, the versions are
incompatible because the newer version was not built for the ppc architecture.
cmpdylib /System/Library/Frameworks/Foundation.framework/Foundation Foundation_proj/Foundation
cmpdylib: file: Foundation_proj/Foundation does not contain architecture: ppc
cmpdylib: new dynamic shared library: Foundation_proj/Foundation does not contain architecture ppc
DIAGNOSTICS
The exit status is zero if the library versions are compatible and nonzero if they are incompatible.
BUGS
There are lots of other things that could be checked for that are not (such as the Objective C API).
Apple Computer, Inc. November 3, 1997 CMPDYLIB(1)