Sponsored Content
Top Forums UNIX for Advanced & Expert Users -pg incompatible with -shared Post 302094966 by jim mcnamara on Thursday 2nd of November 2006 09:46:43 AM
Old 11-02-2006
One choice -

Don't compile a shared library - create an archive ie., library.a Then you can link against it for profiling.

Note: monitor normally records time in and calls to library members when the library is compiled normally but the "local" code is compiled -pg Yours should do that, so it will show up in a profiler.
 

8 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

rpc.rstatd: incompatible...

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

UNIX patches with incompatible packages

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

gcc 4.3.2 accept sys call warrning incompatible pointer type

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

GCC - Incompatible Pointer Types

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

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

6. Red Hat

Incompatible Level of gcc?

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

Incompatible data type fpos_t in C

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

Incompatible types for returned object

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
MPI_Pcontrol(3OpenMPI)													    MPI_Pcontrol(3OpenMPI)

NAME
MPI_Pcontrol - Controls profiling. SYNTAX
C Syntax #include <mpi.h> int MPI_Pcontrol(const int level, ... ) Fortran Syntax INCLUDE 'mpif.h' MPI_PCONTROL(LEVEL) INTEGER LEVEL, ... C++ Syntax #include <mpi.h> void Pcontrol(const int level, ...) INPUT PARAMETER
level Profiling level. DESCRIPTION
MPI libraries themselves make no use of this routine; they simply return immediately to the user code. However the presence of calls to this routine allows a profiling package to be explicitly called by the user. Since MPI has no control of the implementation of the profiling code, we are unable to specify precisely the semantics that will be pro- vided by calls to MPI_Pcontrol. This vagueness extends to the number of arguments to the function, and their datatypes. However to provide some level of portability of user codes to different profiling libraries, we request the following meanings for certain values of level: o level==0 Profiling is disabled. o level==1 Profiling is enabled at a normal default level of detail. o level==2 Profile buffers are flushed. (This may be a no-op in some profilers). o All other values of level have profile library-defined effects and additional arguments. We also request that the default state after MPI_Init has been called is for profiling to be enabled at the normal default level (i.e., as if MPI_Pcontrol had just been called with the argument 1). This allows users to link with a profiling library and obtain profile output without having to modify their source code at all. The provision of MPI_Pcontrol as a no-op in the standard MPI library allows users to modify their source code to obtain more detailed pro- filing information, but still be able to link exactly the same code against the standard MPI library. NOTES
This routine provides a common interface for profiling control. The interpretation of level and any other arguments is left to the profil- ing library. This function does not return an error value. Consequently, the result of calling it before MPI_Init or after MPI_Finalize is undefined. Open MPI 1.2 September 2006 MPI_Pcontrol(3OpenMPI)
All times are GMT -4. The time now is 11:07 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy