Sponsored Content
Top Forums Programming Creation and Accessing Shared Objects (.so) Post 302231983 by Franklin52 on Wednesday 3rd of September 2008 03:23:12 PM
Old 09-03-2008
There are lots of information available on the net, Google for unix shared libraries.

Regards
 

10 More Discussions You Might Find Interesting

1. Programming

Runtime Linking shared Objects

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

Shared memory and C++ Objects (cont)

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

Shared Objects

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

Linking with shared objects

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

Shared Objects

Hi. Does anyone know by how much a text size of an executable(on ibm) would grow if you link one shared object(library)? Is it a constant number or it depends on a .so that is linked? (3 Replies)
Discussion started by: Yura
3 Replies

6. UNIX for Advanced & Expert Users

debugging shared objects

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

7. AIX

Wrong Shared objects getting loaded

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

8. Programming

g++ with -frepo and shared objects...

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

9. Linux

Make file for shared objects

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

Shared objects -urgent please help me out

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
<sys/mman.h>(P) 					     POSIX Programmer's Manual						   <sys/mman.h>(P)

NAME
sys/mman.h - memory management declarations SYNOPSIS
#include <sys/mman.h> DESCRIPTION
The <sys/mman.h> header shall be supported if the implementation supports at least one of the following options: * The Memory Mapped Files option * The Shared Memory Objects option * The Process Memory Locking option * The Memory Protection option * The Typed Memory Objects option * The Synchronized Input and Output option * The Advisory Information option * The Typed Memory Objects option If one or more of the Advisory Information, Memory Mapped Files, or Shared Memory Objects options are supported, the following protection options shall be defined: PROT_READ Page can be read. PROT_WRITE Page can be written. PROT_EXEC Page can be executed. PROT_NONE Page cannot be accessed. The following flag options shall be defined: MAP_SHARED Share changes. MAP_PRIVATE Changes are private. MAP_FIXED Interpret addr exactly. The following flags shall be defined for msync(): MS_ASYNC Perform asynchronous writes. MS_SYNC Perform synchronous writes. MS_INVALIDATE Invalidate mappings. The following symbolic constants shall be defined for the mlockall() function: MCL_CURRENT Lock currently mapped pages. MCL_FUTURE Lock pages that become mapped. The symbolic constant MAP_FAILED shall be defined to indicate a failure from the mmap() function. If the Advisory Information and either the Memory Mapped Files or Shared Memory Objects options are supported, values for advice used by posix_madvise() shall be defined as follows: POSIX_MADV_NORMAL The application has no advice to give on its behavior with respect to the specified range. It is the default characteristic if no advice is given for a range of memory. POSIX_MADV_SEQUENTIAL The application expects to access the specified range sequentially from lower addresses to higher addresses. POSIX_MADV_RANDOM The application expects to access the specified range in a random order. POSIX_MADV_WILLNEED The application expects to access the specified range in the near future. POSIX_MADV_DONTNEED The application expects that it will not access the specified range in the near future. The following flags shall be defined for posix_typed_mem_open(): POSIX_TYPED_MEM_ALLOCATE Allocate on mmap(). POSIX_TYPED_MEM_ALLOCATE_CONTIG Allocate contiguously on mmap(). POSIX_TYPED_MEM_MAP_ALLOCATABLE Map on mmap(), without affecting allocatability. The mode_t, off_t, and size_t types shall be defined as described in <sys/types.h> . The <sys/mman.h> header shall define the structure posix_typed_mem_info, which includes at least the following member: size_t posix_tmi_length Maximum length which may be allocated from a typed memory object. The following shall be declared as functions and may also be defined as macros. Function prototypes shall be provided. int mlock(const void *, size_t); int mlockall(int); void *mmap(void *, size_t, int, int, int, off_t); int mprotect(void *, size_t, int); int msync(void *, size_t, int); int munlock(const void *, size_t); int munlockall(void); int munmap(void *, size_t); int posix_madvise(void *, size_t, int); int posix_mem_offset(const void *restrict, size_t, off_t *restrict, size_t *restrict, int *restrict); int posix_typed_mem_get_info(int, struct posix_typed_mem_info *); int posix_typed_mem_open(const char *, int, int); int shm_open(const char *, int, mode_t); int shm_unlink(const char *); The following sections are informative. APPLICATION USAGE
None. RATIONALE
None. FUTURE DIRECTIONS
None. SEE ALSO
<sys/types.h> , the System Interfaces volume of IEEE Std 1003.1-2001, mlock(), mlockall(), mmap(), mprotect(), msync(), munlock(), munlock- all(), munmap(), posix_mem_offset(), posix_typed_mem_get_info(), posix_typed_mem_open(), shm_open(), shm_unlink() COPYRIGHT
Portions of this text are reprinted and reproduced in electronic form from IEEE Std 1003.1, 2003 Edition, Standard for Information Technol- ogy -- Portable Operating System Interface (POSIX), The Open Group Base Specifications Issue 6, Copyright (C) 2001-2003 by the Institute of Electrical and Electronics Engineers, Inc and The Open Group. In the event of any discrepancy between this version and the original IEEE and The Open Group Standard, the original IEEE and The Open Group Standard is the referee document. The original Standard can be obtained online at http://www.opengroup.org/unix/online.html . IEEE
/The Open Group 2003 <sys/mman.h>(P)
All times are GMT -4. The time now is 07:29 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy