>
> My first step was to have profiled versions of these libraries built in
> the hope that I could use them to isolate where the additional cycles
> were being burned. Several builds and profiled runs later, and after a
> fair amount of searching the Internet, I've concluded that I'll never
> get anything out of shared objects instrumented with GCC; all code to be
> profiled must be statically linked. If you know this to be untrue,
> please let me know! :) My plan now is to build static versions of all
> GTK libraries instrumented for profiling and link against those.
>
I would suggest to use a sampling profiler, like oprofile, sysprof, but all
those are linux profilers (they need a kernel module). But I am sure there a
sampling profilers for solaris too. The advantage is that you don't need to
recompile your apps (given you have debug symbols alreday) and it works with
shared libs too.
Stefan
> FYI, Our platform is Solaris 10 (x86) compiling with GCC 3.4.
>
> Thanks in advance,
>
> Chris Rorvick
> _______________________________________________
> gtk-app-devel-list mailing list
> gtk-app-devel-list gnome org
> http://mail.gnome.org/mailman/listinfo/gtk-app-devel-list
_______________________________________________
gtk-app-devel-list mailing list
gtk-app-devel-list gnome org
http://mail.gnome.org/mailman/listinfo/gtk-app-devel-list