This seems like a packaging problem, since in the debian world (not
ubuntu) perf happily supports dwarf symbols.

What is the current status? I would be happy to contribute a patch to
fix it, but don't want to redo anyone's work.

Also, is there a reason that the fix could not get backported to older
distros? It doesn't require changing the kernel, just the user space
perf binaries with an update.

Anyone that doesn't have perf tools installed won't notice the change.
And everyone that has perf tools installed (and therefore uses it) will
be very happy; I honestly can't see a reason NOT to do it. perf tools is
an essential component for performance tuning server applications.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1248289

Title:
  Missing libunwind support in perf

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I'm trying to use perf's libunwind support in 13.04 with kernel
  3.11.0-12-generic on amd64.  Typically you can do this by using the
  "-g dwarf" flag, but it appears the perf command included in linux-
  tools-3.11.0-12-generic was not compiled with libunwind.  This may be
  as simple as the build machine didn't have libunwind installed.
  Having dwarf support in perf with default Ubuntu kernels would be very
  useful as it provides a way to get profiling information when
  -fomitframepointer is used.

  Relevant upstream code:

  https://github.com/torvalds/linux/blob/v3.11/tools/perf/Makefile#L459
  https://github.com/torvalds/linux/blob/v3.11/tools/perf/builtin-record.c#L758

  Let me know if I can provide any other information.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1248289/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to     : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to