06-11-2010
objdump -h /path/to/library.so will tell you what segments exist in what parts of the file, which you can match up with /proc/self/maps' third column(which is the offset mapped to the file). Because of paging considerations they may not match up precisely.
10 More Discussions You Might Find Interesting
1. 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
2. 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
3. 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
4. AIX
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
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. Solaris
Hi,
Im working on Solaris 9 on SPARC-32 bit running on an Ultra-80, and I have to find out the following:-
1. Total Physical Memory in the system(total RAM).
2. Available Physical Memory(i.e. RAM Usage)
3. Total (Logical) Memory in the system
4. Available (Logical) Memory.
I know... (4 Replies)
Discussion started by: 0ktalmagik
4 Replies
7. Solaris
Is it possible to restrict physical memory in solaris zone with zone.max-locked-memory just like we can do with rcapd ? I do not want to used rcapd (1 Reply)
Discussion started by: fugitive
1 Replies
8. 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
9. 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
10. 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
size(1) User Commands size(1)
NAME
size - print section sizes in bytes of object files
SYNOPSIS
size [-f] [-F] [-n] [-o] [-V] [-x] filename...
DESCRIPTION
The size command produces segment or section size information in bytes for each loaded section in ELF object files. size prints out the
size of the text, data, and bss (uninitialized data) segments (or sections) and their total.
size processes ELF object files entered on the command line. If an archive file is input to the size command, the information for each
object file in the archive is displayed.
When calculating segment information, the size command prints out the total file size of the non-writable segments, the total file size of
the writable segments, and the total memory size of the writable segments minus the total file size of the writable segments.
If it cannot calculate segment information, size calculates section information. When calculating section information, it prints out the
total size of sections that are allocatable, non-writable, and not NOBITS, the total size of the sections that are allocatable, writable,
and not NOBITS, and the total size of the writable sections of type NOBITS. NOBITS sections do not actually take up space in the filename.
If size cannot calculate either segment or section information, it prints an error message and stops processing the file.
OPTIONS
The following options are supported:
-f Prints out the size of each allocatable section, the name of the section, and the total of the section sizes. If there is no sec-
tion data, size prints out an error message and stops processing the file.
-F Prints out the size of each loadable segment, the permission flags of the segment, then the total of the loadable segment sizes.
If there is no segment data, size prints an error message and stops processing the file.
-n Prints out non-loadable segment or non-allocatable section sizes. If segment data exists, size prints out the memory size of each
loadable segment or file size of each non-loadable segment, the permission flags, and the total size of the segments. If there is
no segment data, size prints out, for each allocatable and non-allocatable section, the memory size, the section name, and the
total size of the sections. If there is no segment or section data, size prints an error message and stops processing.
-o Prints numbers in octal, not decimal.
-V Prints the version information for the size command on the standard error output.
-x Prints numbers in hexadecimal, not decimal.
EXAMPLES
The examples below are typical size output.
Example 1: Producing size information
example% size filename
2724 + 88 + 0 = 2812
Example 2: Producing allocatable section size information
example% size -f filename
26(.text) + 5(.init) + 5(.fini) = 36
Example 3: Producing loadable segment size information
example% size -F filename
2724(r-x) + 88(rwx) + 0(rwx) = 2812 ... (If statically linked)
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWbtool |
+-----------------------------+-----------------------------+
SEE ALSO
as(1), cc(1B), ld(1), ar.h(3HEAD), a.out(4), attributes(5)
NOTES
Since the size of bss sections is not known until link-edit time, the size command will not give the true total size of pre-linked objects.
SunOS 5.10 16 Oct 1996 size(1)