From: Mark Nelson <mnelson@redhat.com>
To: Sage Weil <sweil@redhat.com>
Cc: ceph-devel@vger.kernel.org
Subject: Re: -fno-omit-frame-pointer
Date: Mon, 23 Feb 2015 15:35:19 -0600 [thread overview]
Message-ID: <54EB9D17.7090509@redhat.com> (raw)
In-Reply-To: <54E91449.4090000@redhat.com>
On 02/21/2015 05:27 PM, Mark Nelson wrote:
> I've still had the best luck using DWARF though. I was able to get much
> better stack traces with it. A semi-modern kernel with libunwind
> support in perf is needed though. I just checked one of our RHEL7 and
> it sadly doesn't look like they have it linked. We really should hassle
> them to get this in. Perf on our Ubuntu 14.04 does use libunwind,
> primarily due to the kernel bug we submitted:
>
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1248289
FWIW, I followed up with the RHEL7 kernel guys who pointed out that
while RHEL 7.0 doesn't have dwarf support in perf, 7.1 does, and it's
using what appears to be a better libdw unwind implementation:
http://lwn.net/Articles/579508/
>
> Mark
> --
> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2015-02-23 21:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-21 21:43 -fno-omit-frame-pointer Sage Weil
2015-02-21 22:09 ` -fno-omit-frame-pointer Alex Elsayed
2015-02-21 23:27 ` -fno-omit-frame-pointer Mark Nelson
2015-02-23 18:28 ` -fno-omit-frame-pointer Sage Weil
2015-02-23 18:30 ` -fno-omit-frame-pointer Sage Weil
2015-02-23 21:35 ` Mark Nelson [this message]
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=54EB9D17.7090509@redhat.com \
--to=mnelson@redhat.com \
--cc=ceph-devel@vger.kernel.org \
--cc=sweil@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.