On Fri, 4 Mar 2011, Gregory Farnum wrote: > 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... Yeah. If it's not going to be reliable, though, it's not worth investing time/debugging effort into making it (sort of) work. I suspect oprofile is the way to go here... sage -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
