03-01-2005
Maybe 'objdump' with suitable option will help you.
Regards
10 More Discussions You Might Find Interesting
1. Programming
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
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. Programming
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
4. UNIX for Advanced & Expert Users
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
5. UNIX for Advanced & Expert Users
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
6. 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
7. Programming
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
8. Programming
Hi,
I am looking for references about creating and accessing Shared Objects (.so) through C/C++ on Unix / Linux platforms. Is it possible and where can I find the info.
Thanks
Phil (1 Reply)
Discussion started by: phil nascimento
1 Replies
9. Linux
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
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
LEARN ABOUT V7
opannotate
OPANNOTATE(1) General Commands Manual OPANNOTATE(1)
NAME
opannotate - produce source or assembly annotated with profile data
SYNOPSIS
opannotate [ options ] [profile specification]
DESCRIPTION
opannotate outputs annotated source and/or assembly from profile data of an OProfile session. See oprofile(1) for how to write profile
specifications.
OPTIONS
--assembly / -a
Output annotated assembly. If this is combined with --source, then mixed source / assembly annotations are output.
--demangle / -D none|smart|normal
none: no demangling. normal: use default demangler (default) smart: use pattern-matching to make C++ symbol demangling more read-
able.
--exclude-dependent / -x
Do not include application-specific images for libraries, kernel modules and the kernel. This option only makes sense if the profile
session used --separate.
--exclude-file [files]
Exclude all files in the given comma-separated list of glob patterns.
--exclude-symbols / -e [symbols]
Exclude all the symbols in the given comma-separated list.
--help / -? / --usage
Show help message.
--image-path / -p [paths]
Comma-separated list of additional paths to search for binaries. This is needed to find modules in kernels 2.6 and upwards.
--root / -R [path]
A path to a filesystem to search for additional binaries.
--include-file [files]
Only include files in the given comma-separated list of glob patterns.
--include-symbols / -i [symbols]
Only include symbols in the given comma-separated list.
--objdump-params [params]
Pass the given parameters as extra values when calling objdump.
--output-dir / -o [dir]
Output directory. This makes opannotate output one annotated file for each source file. This option can't be used in conjunction
with --assembly.
--search-dirs / -d [paths]
Comma-separated list of paths to search for source files. You may need to use this option when the debug information for an image
contains relative paths.
--base-dirs / -b [paths]
Comma-separated list of paths to strip from debug source files, prior to looking for them in --search-dirs.
--session-dir=dir_path
Use sample database out of directory dir_path instead of the default location (/var/lib/oprofile).
--source / -s
Output annotated source. This requires debugging information to be available for the binaries.
--threshold / -t [percentage]
Only output data for symbols that have more than the given percentage of total samples.
--verbose / -V [options]
Give verbose debugging output.
--version / -v
Show version.
ENVIRONMENT
No special environment variables are recognised by opannotate.
FILES
/var/lib/oprofile/samples/
The location of the generated sample files.
VERSION
This man page is current for oprofile-0.9.6.
SEE ALSO
/usr/share/doc/oprofile/, oprofile(1)
4th Berkeley Distribution Tue 06 July 2010 OPANNOTATE(1)