I'm sorry you didn't get any help. But I would like to note that gprof is generally not considered a good tool for profiling, especially if threads are involved. People suggest statistical profilers like perf (Linux kernel profiler, works in userspace too), gperftools, oprofile, dtrace (not just a profiler). If you have a mac you can use its GUI for dtrace. If you are adventurous you can use the Linux equivalents of dtrace called systemtap and LTTng. Jon Nordby likes gperftools IIRC, you can analyse its output with kcachegrind. For perf you can use gprof2dot to get a graphical callgraph instead of the CLI one. On Sun, Mar 10, 2013 at 12:51 AM, Tibor Bamhor <tiborb95@xxxxxxxxx> wrote: > Hi, > > I reply to my own post. On the second time using gprof turned to be easy. In > case anybody is interested, the steps are: _______________________________________________ gimp-developer-list mailing list gimp-developer-list@xxxxxxxxx https://mail.gnome.org/mailman/listinfo/gimp-developer-list
