Re: How to profile?

[Helge Hess]

Hi,

'profile=yes' makes gcc embed profiling information in the binary. Read
the 'gprof' man page to find out more about it. It provides profiling
information for all function calls. AFAIK it only works with non-shared
binaries.

Greetings
  Helge

Michael Hanni wrote:
> 
> I'm trying to optimize some display code in gstep-gui.  To see where I
> can better target my work I'd like to profile the library with the
> testing apps and see where bottlenecks are.  What is the proper way of
> doing this?  I've attempted to use debug=yes profile=yes, but this only
> provides very basic profilling data of message passing and classes
> within the test app, but not anything from within the AppKit.  I find it
> hard to believe that none of the gstep-gui classes are costing time when
> I can visually see that there are things in the AppKit that are not
> "snappy"... Anyhow, any ideas?
> 
> Cheers,
> 
>   Michael
> 
> _______________________________________________
> Discuss-gnustep mailing list
> Discuss-gnustep@gnu.org
> http://mail.gnu.org/mailman/listinfo/discuss-gnustep

-- 
SKYRIX Software Solutions - http://www.skyrix.com
Visit us at the Systems 2000 - LinuxPark - Munich