All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gregory Farnum <gregory.farnum@dreamhost.com>
To: Colin McCabe <cmccabe@alumni.cmu.edu>
Cc: ceph-devel@vger.kernel.org
Subject: Re: about cpu_profiler
Date: Fri, 4 Mar 2011 12:40:05 -0800	[thread overview]
Message-ID: <00BB198CFBE347429653477BED3AA89B@gmail.com> (raw)
In-Reply-To: <AANLkTimYykJpXQF3qUPYA7OF2jUf55WruXje1q0xJTet@mail.gmail.com>


On Friday, March 4, 2011 at 12:08 PM, Colin McCabe wrote: 
> tl;dr: cpu_profiler may randomly crash your program on x86_64.
> The problem "should" be resolved in the "future".

From what I've read, it's unfortunately not out of date. However, it manifests itself as a crash so it's not the reason that we can't get debugging output, unless there's something I'm missing. :)
And even if it turns out to be very unstable on x86-64, the value of a good cpu profiler is high enough that we can set up x86 boxes or VMs...
-Greg 




  reply	other threads:[~2011-03-04 20:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-04 20:08 about cpu_profiler Colin McCabe
2011-03-04 20:40 ` Gregory Farnum [this message]
2011-03-04 20:45   ` Sage Weil
2011-03-04 20:47   ` Colin McCabe
2011-03-05  2:17     ` Colin McCabe

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=00BB198CFBE347429653477BED3AA89B@gmail.com \
    --to=gregory.farnum@dreamhost.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=cmccabe@alumni.cmu.edu \
    /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.