Sponsored Content
Top Forums Programming function profiler for HPUX...? Post 58299 by PxT on Wednesday 17th of November 2004 03:02:46 PM
Old 11-17-2004
See the man pages for profil(2) and monitor(3c)
 

4 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Need Script to Use CPUs on a HPUX server to simulate Workload Manager on HPUX.

I am running HPUX and using WLM (workload manager). I want to write a script to fork CPUs to basically take CPUs from other servers to show that the communication is working and CPU licensing is working. Basically, I want to build a script that will use up CPU on a server. Any ideas? (2 Replies)
Discussion started by: cpolikowsky
2 Replies

2. Programming

C/C++ Appliaction Profiler

Dear All, I have my C/C++ appliaction running on Sun Solaris 5.9. Can any of you please suggest a profiler which i can use for improving the code performance. Please reply as i am stuck with the performance of the code. (1 Reply)
Discussion started by: ashisharora
1 Replies

3. Shell Programming and Scripting

profiler

What is a hard and soft match in unix profiler ??? (1 Reply)
Discussion started by: ekharvi
1 Replies

4. HP-UX

pwage-hpux-T for Trusted HPUX servers

I'm sharing this in case anybody needs it. Modified from the original solaris pwage script. This modified hpux script will check /etc/password file on hpux trusted systems search /tcb and grep the required u_succhg field. Calculate days to expiry and notify users via email. original solaris... (2 Replies)
Discussion started by: sparcguy
2 Replies
MONITOR(3)						     Library Functions Manual							MONITOR(3)

NAME
monitor - prepare execution profile SYNOPSIS
monitor(lowpc, highpc, buffer, bufsize, nfunc) int (*lowpc)( ), (*highpc)( ); short buffer[ ]; DESCRIPTION
An executable program created by `cc -p' automatically includes calls for monitor with default parameters; monitor needn't be called explicitly except to gain fine control over profiling. Monitor is an interface to profil(2). Lowpc and highpc are the addresses of two functions; buffer is the address of a (user supplied) array of bufsize short integers. Monitor arranges to record a histogram of periodically sampled values of the program counter, and of counts of calls of certain functions, in the buffer. The lowest address sampled is that of lowpc and the highest is just below highpc. At most nfunc call counts can be kept; only calls of functions compiled with the profiling option -p of cc(1) are recorded. For the results to be significant, especially where there are small, heavily used routines, it is suggested that the buffer be no more than a few times smaller than the range of locations sampled. To profile the entire program, it is sufficient to use extern etext(); ... monitor((int)2, etext, buf, bufsize, nfunc); Etext lies just above all the program text, see end(3). To stop execution monitoring and write the results on the file mon.out, use monitor(0); then prof(1) can be used to examine the results. FILES
mon.out SEE ALSO
prof(1), profil(2), cc(1) MONITOR(3)
All times are GMT -4. The time now is 02:06 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy