1825776 Members
2081 Online
109687 Solutions
New Discussion

HP-UX

 
jr_8
New Member

HP-UX

What profiler should we use for HP-UX 11i v2.0
9 REPLIES 9
Shannon Petry
Honored Contributor

Re: HP-UX

Can you phrase a more precise question? If it were just a bit more vague, I'd answer 42. :^)


Shannon
Microsoft. When do you want a virus today?
Pete Randall
Outstanding Contributor

Re: HP-UX

Can you elaborate on what you mean by "profiler"?


Pete


Pete
Brian Bergstrand
Honored Contributor

Re: HP-UX

Are you talking about a code profiler? If so use the one that came with the compiler. Eg. gprof for gcc. Otherwise, could you clarify what you mean by profiler?
jr_8
New Member

Re: HP-UX

How about, what debugger should we use for HP-UX 11i v2.0?
Mark Greene_1
Honored Contributor

Re: HP-UX

see the man page for adb

mark
the future will be a lot like now, only later
Brian Bergstrand
Honored Contributor

Re: HP-UX

Again, depends on what compiler you are using. For gcc (stabs format) use gdb. For UX compiler there is adb, etc.

HTH.
Robert-Jan Goossens
Honored Contributor

Re: HP-UX

The HP WDB debugger is based on GDB and is free software. You may download the source, executable, and documentation to use and/or modify as you wish.

http://h21007.www2.hp.com/dspp/tech/tech_TechSoftwareDetailPage_IDX/1,1703,1667,00.html

Hope it helps,

Robert-Jan.
Brian Bergstrand
Honored Contributor

Re: HP-UX

Forgot to mention:

If you are using HP's compiler, then you'll want to look at hiprof and pixie for profiling code.
Mike Stroyan
Honored Contributor

Re: HP-UX

There are two very good choices for profiling on HP-UX 11i v2.0.

Caliper is the best choice for a process profiler. It ships in /opt/caliper/bin/caliper as part of the C or C++ compiler bundles. Documentation and the latest version is also available at
http://www.hp.com/go/caliper
Caliper can produce many kinds of reports including flat profiles, call graph profiles, and detailed information gathered from the Itanium CPUs' performance monitor. It does not require any special compiler options. It can gather profile data for most any native executable. It can even be used with java to profile interpreted code, hotspot compiled code, and JNI native code.

Prospect is another good profiling tool. It is available at
http://www.hp.com/go/prospect
Prospect produces flat profiles of process code. It has some advantages over caliper. It can report on multiple processes at once, either descendents of a target process or all processes in the system. It will report the time processes spend in system calls and profiles of kernel functions.

There are many other performance technologies discussed at
http://h21007.www2.hp.com/dspp/dev/technologies/topic/1,2608,10313,00.html

The first choice for debugging on HP-UX 11i v2.0 is wdb. It ships with the compilers in /opt/langtools/bin/wdb. Documentation and the latest version is also available at
http://www.hp.com/go/wdb
Wdb puts a graphical front-end on gdb, or you can use it with a plain gdb command line.

If you use the vi text editor, then you might want to try firebolt. It is an IDE based on gvim. It provides integration of text editing, building, and debugging. It is available from
http://h21007.www2.hp.com/dspp/tech/tech_TechSoftwareDetailPage_IDX/1,1703,3325,00.html