11-02-2006
The error message means what it says -- gprof won't work for shared libraries. It's not a bug, gprof's just not meant for it. You'll need to link it statically or use something else.
If you use Linux, you might find
sysprof useful. It'd probably do
better on shared libraries than executables since shared libraries by definition have symbol information...
8 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hi,
I'm working with Mercury tools: Loadrunner, and I'm trying to monitor a unix server by rstatd, and I got next error:
Mar 4 11:25:56 sacindt rpc.rstatd: incompatible to /proc. Could not read disk_io: data
does any one have an idea about this..
regards (0 Replies)
Discussion started by: toto2000ff
0 Replies
2. UNIX for Advanced & Expert Users
I have a Sun Sparc machine with Solaris 9 on it as oracle server. We added two patches (112233-11: SunOS 5.9:Kernel Patch and 111722-04: SunOS 5.9:MathLibrary(libm)patch). When I prepared the server for Oracle installation, I checked patch with command: $/usr/sbin/patchadd -p | grep <patch_number>.... (0 Replies)
Discussion started by: duke0001
0 Replies
3. Programming
Hi all, this warning is driving me nuts. I use -pedantic with -Wall and -Werror so this needs to be fixed.
BUILD: GNU-Linux-x86
Any ideas?
struct sockaddr_in server_addr;
int addr_len = sizeof (server_addr);
fd = accept(link->socket_fd,
(struct sockaddr_in *)... (2 Replies)
Discussion started by: personificator
2 Replies
4. Programming
Hi guys,
here is my code written in C and the compiler error message.
int i;
int (*a);
for (i = 1;i <= 9;i++)
a = (int *)malloc(sizeof(int) * 10);here is the error:
incompatible types when assigning to type ‘int’ from type ‘int *’I want to make a two dimensional array. I... (2 Replies)
Discussion started by: majid.merkava
2 Replies
5. 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
6. Red Hat
I'm compiling an application someone gave me. It uses XLC on a Power7, running Red Hat (4? 5?). It compiles and links, but I get the following message for every .o and .exe...
xlc_r: 1501-274 (W) An incompatible level of gcc has been specified.
I've tried googling on this error, and I'll I... (2 Replies)
Discussion started by: Harper21
2 Replies
7. Programming
This is from a program I wrote over in 1998 that I am trying to compile on a linux machine:
void write_line (FILE *fp, int rec_no, line_rec *arec)
{
fpos_t woffset;
woffset = (rec_no - 1) * sizeof(line_rec);
fsetpos(fp,&woffset);
fwrite(arec,sizeof(line_rec),1,fp);
}On the line... (2 Replies)
Discussion started by: wbport
2 Replies
8. Programming
I have a function from the Sedgewick's book
// return the shortest path from v to s as an Iterable
public Iterable<String> pathTo(String v) {
Stack<String> path = new Stack<String>();
while (v != null && dist.contains(v)) {
path.push(v);
v =... (2 Replies)
Discussion started by: yifangt
2 Replies
LIBBASH(7) libbash Manual LIBBASH(7)
NAME
libbash -- A bash shared libraries package.
DESCRIPTION
libbash is a package that enables bash dynamic-like shared libraries. Actually its a tool for managing bash scripts whose functions you may
want to load and use in scripts of your own.
It contains a 'dynamic loader' for the shared libraries ( ldbash(1)), a configuration tool (ldbashconfig(8)), and some libraries.
Using ldbash(1) you are able to load loadable bash libraries, such as getopts(1) and hashstash(1). A bash shared library that can be loaded
using
ldbash(1) must answer 4 requirments:
1. It must be installed in $LIBBASH_PREFIX/lib/bash (default is /usr/lib/bash).
2. It must contain a line that begins with '#EXPORT='. That line will contain (after the '=') a list of functions that the library
exports. I.e. all the function that will be usable after loading that library will be listed in that line.
3. It must contain a line that begins with '#REQUIRE='. That line will contain (after the '=') a list of bash libraries that are
required for our library. I.e. every bash library that is in use in our bash library must be listed there.
4. The library must be listed (For more information, see ldbashconfig(8)).
Basic guidelines for writing library of your own:
1. Be aware, that your library will be actually sourced. So, basically, it should contain (i.e define) only functions.
2. Try to declare all variables intended for internal use as local.
3. Global variables and functions that are intended for internal use (i.e are not defined in '#EXPORT=') should begin with:
__<library_name>_
For example, internal function myfoosort of hashstash library should be named as
__hashstash_myfoosort
This helps to avoid conflicts in global name space when using libraries that come from different vendors.
4. See html manual for full version of this guide.
AUTHORS
Hai Zaar <haizaar@haizaar.com>
Gil Ran <ril@ran4.net>
SEE ALSO
ldbash(1), ldbashconfig(8), getopts(1), hashstash(1) colors(1) messages(1) urlcoding(1) locks(1)
Linux Epoch Linux