From: Ben Elliston <bje@au1.ibm.com>
To: James E Wilson <wilson@specifix.com>
Cc: binutils@sourceware.org
Subject: Re: curious gprof behaviour on trivial testcase
Date: Tue, 02 May 2006 00:33:00 -0000 [thread overview]
Message-ID: <20060502003353.GA32356@ozlabs.au.ibm.com> (raw)
In-Reply-To: <1146276484.15759.326.camel@aretha.corp.specifix.com>
Hi Jim
> The problem here is that a trivial testcase has only one function,
> and hence no call graph info. However, gprof by default assumes you
> want to emit call graph info, and if there is none, it gives an
> error.
Thanks for fixing this -- it caught me recently and I didn't get a
chance to go back and try to fix it myself.
More to the point, the error message you get from gprof is utterly
unhelpful. When I encountered it, I immediately suspected corruption
in the gmon.out file or operator error. It had me scratching my head
for a bit!
Cheers, Ben
next prev parent reply other threads:[~2006-05-02 0:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-29 16:56 James E Wilson
2006-04-29 18:49 ` Daniel Jacobowitz
2006-05-02 0:33 ` Ben Elliston [this message]
2006-05-02 10:55 ` Nick Clifton
2006-05-02 18:03 ` James E Wilson
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=20060502003353.GA32356@ozlabs.au.ibm.com \
--to=bje@au1.ibm.com \
--cc=binutils@sourceware.org \
--cc=wilson@specifix.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).