From: Stephen Wynne <stevemw@mindspring.com>
To: egcs@egcs.cygnus.com
Subject: Gprof, pthreads, and Shared Libs on Linux glibc?
Date: Fri, 25 Dec 1998 09:41:00 -0000 [thread overview]
Message-ID: <199812251739.MAA07795@fuji.homenet> (raw)
On Linux with glibc-2.0.7-20 I'm attempting to profile a
multi-threaded (LinuxThreads) app that uses a lot of shared libraries.
In the gprof(1) output, I get call graphs but no timing information.
Does anyone have any tips, even just hints about getting performance
data out of egcs in general?
(I picked up the glibc's from
http://odin.appliedtheory.com/debug_thread_rpms/RedHat_5.1/RPMS/i386/ ,
I'm running egcs-1.1b, and I happen to be on RedHat 5.0.)
Do *all* of my libraries have to be compiled with profiling
information in order to get *any* timing data? For example, I don't
see any profiled X11 libraries on my system. Do I need to link
statically when I give the -pg flag to egcs? Do pthreads pretty
much make profiling impossible?
I'm building the latest Blackdown JDK in an effort to help track some
performance problems, so any help would be appreciated!
reply other threads:[~1998-12-25 9:41 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=199812251739.MAA07795@fuji.homenet \
--to=stevemw@mindspring.com \
--cc=egcs@egcs.cygnus.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).