From: Sriranga Veeraraghavan <ranga@CSUA.Berkeley.EDU>
To: linuxppc-dev@lists.linuxppc.org
Subject: Profiling Code
Date: Mon, 20 Sep 1999 00:48:48 -0700 [thread overview]
Message-ID: <199909200748.AAA10294@soda.CSUA.Berkeley.EDU> (raw)
Hi,
I have been trying to profile a small C program under LinuxPPC, but I
can't gprof to run. (I couldn't find prof on my box).
Bascially my make rule for profiling executes the following code:
$ gcc -pg -Wall -pedantic -o prog prog.c
This compiles just fine. When I execute the program it creates the
gmon.out file correctly. If I run gprof against this gmon.out file, I
get a seg fault:
$ gprof prog gmon.out
Segmentation fault
ldd on gprof looks okay:
$ ldd /usr/bin/gprof
libbfd-990418.so => /usr/lib/libbfd-990418.so (0x01753000)
libc.so.6 => /lib/libc.so.6 (0x01611000)
/lib/ld.so.1 => /lib/ld.so.1 (0x30000000)
I am able to build with profiling on my Solaris box and Linux x86 just
fine (for the exact same program), so I think that I'm not doing
something correctly on PPC.
If anyone has been able profile thier code under LinuxPPC, I would
appreciate some pointers.
Thanks,
----ranga <ranga@soda.berkeley.edu>
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
reply other threads:[~1999-09-20 7:48 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=199909200748.AAA10294@soda.CSUA.Berkeley.EDU \
--to=ranga@csua.berkeley.edu \
--cc=linuxppc-dev@lists.linuxppc.org \
/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 NNTP newsgroup(s).