Sponsored Content
Full Discussion: Shared Library Issue HP UX
Operating Systems HP-UX Shared Library Issue HP UX Post 302342956 by sambarusty on Tuesday 11th of August 2009 05:51:14 PM
Old 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

Shared Library

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

shared library

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

Shared memory in shared library

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

Using funcion in a shared library

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

Shared memory for shared library

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

How to change a Makefile from building static library to shared library?

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

Overhead of using a shared library

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)

Linking to a shared library

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

Shared library with acces to shared memory.

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

Add shared members from library to same library in a different directory

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
REDO_PREBINDING(1)					      General Commands Manual						REDO_PREBINDING(1)

NAME
redo_prebinding - redo the prebinding of an executable or dynamic library SYNOPSIS
redo_prebinding [-c | -p | -d] [-i] [-z] [-u] [-r rootdir] [-e executable_path] [-seg_addr_table table_file_name] [-seg_addr_table_filename pathname] [-seg1addr address] [-o output_file] [-s] input_file DESCRIPTION
Redo_prebinding is used to redo the prebinding of an executable or dynamic library when one of the dependent dynamic libraries changes. The input file, executable or dynamic library, must have initially been prebound for this program to redo the prebinding. Also all depended libraries must have their prebinding up to date. So when redoing the prebinding for libraries they must be done in dependency order. Also when building executables or dynamic libraries that are to be prebound (with the -prebind options to ld(1) or libtool(1)) the dependent libraries must have their prebinding up to date or the result will not be prebound. The options allow for different types of checking for use in shell scripts. Only one of -c, -p or -d can be used at a time. If redo_pre- binding redoes the prebinding on an input file it will run /usr/bin/objcunique if it exists on the result. OPTIONS
-c only check if the file needs to have it's prebinding redone and return status. A 0 exit means the file's prebinding is up to date, 1 means it needs to be redone and 2 means it could not be checked for reasons like a dependent library is missing (an error message is printed in these cases). -p check only for prebound files and return status. An exit status of 1 means the file is a Mach-O that could have been prebound and is not otherwise the exit status is 0. -d check only for dynamic shared library files and return status. An exit status of 0 means the file is a dynamic shared library, 1 means the file is not, 2 means there is some mix in the architectures. -i ignore non-prebound files (useful when running on all types of files). -z zero out the prebind check sum in the output if it has one. -u unprebind, rather than reprebind (-c, -p, -d, -e ignored). Resets or removes prebinding-specific information from the input file. As unprebinding is intended to produce a canonical Mach-O binary, bundles and non-prebound executables and dylibs are acceptable as input. For these files, the unprebind operation will zero library time stamps and version numbers and zero entries in the two- level hints table. -e executable_path replace any dependent library's "@executable_path" prefix with the executable_path argument. -seg_addr_table table_file_name The -seg_addr_table option is used when the input a dynamic library and if specified the table entry for the install_name of the dynamic library is used for checking and the address to relocate the library to as it prefered address. -seg_addr_table_filename pathname Use pathname instead of the install name of the library for matching an entry in the segment address table. -seg1addr address Move the input library to base address address. This option does not apply when -u, -seg_addr_table or -seg_addr_table_filename are specified. -r rootdir prepend the rootdir argument to all dependent libraries. -o output_file write the updated file into output_file rather than back into the input file. -s write the updated file to standard output DIAGNOSTICS
With no -c, -p or -d an exit status of 0 means success and 2 means it could not be done for reasons like a dependent library is missing (an error message is printed in these cases). And exit of 3 is for the specific case when the dependent libraries are out of date with respect to each other. Apple Computer, Inc. March 29, 2004 REDO_PREBINDING(1)
All times are GMT -4. The time now is 04:06 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy