From: Dan Mick <dan.mick@dreamhost.com>
To: ceph-devel <ceph-devel@vger.kernel.org>
Subject: Problem with google-pprof
Date: Fri, 27 Apr 2012 10:10:22 -0700 [thread overview]
Message-ID: <4F9AD2FE.7080508@dreamhost.com> (raw)
I spent some time looking into why google-pprof was broken with
debug-stripped binaries. It relates to an issue with addr2line that I'm
still looking into, but the easy workaround is to add /usr/lib/debug to
the path of the binary you're interested in running analysis on. That
is, instead of
google-pprof <display options> /usr/bin/ceph-osd <profile>
you say
google-pprof <display options> /usr/lib/debug/usr/bin/ceph-osd <profile>
reply other threads:[~2012-04-27 17:10 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=4F9AD2FE.7080508@dreamhost.com \
--to=dan.mick@dreamhost.com \
--cc=ceph-devel@vger.kernel.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