[Kernel-packages] [Bug 1590236] Re: perf --call-graph dwarf doesn't record correct call graph

2016-09-28 Thread Launchpad Bug Tracker 
This bug was fixed in the package libunwind - 1.1-4.1ubuntu1

---
libunwind (1.1-4.1ubuntu1) yakkety; urgency=medium

  * Configure with --enable-debug-frame. LP: #1590236.

 -- Matthias Klose   Mon, 19 Sep 2016 13:28:08 +0200

** Changed in: libunwind (Ubuntu)
   Status: Confirmed => Fix Released

-- 
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/1590236

Title:
  perf --call-graph dwarf doesn't record correct call graph

Status in libunwind package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in libunwind source package in Xenial:
  Confirmed
Status in linux source package in Xenial:
  Confirmed

Bug description:
  1. What you expected to happen
  Profiling program by "perf --call-graph dwarf" shows correct call-graph in 
perf report

  2. What actually happened
  perf report doesn't show correct call graph. Then perf is re-builded from 
source. During building, perf configure detection says stock libunwind's 
debug_frame feature is not enabled. It leads perf can't record program's 
call-graph correctly.

  3. How it is solved on my local machine
a. get libunwind source by apt-get source libunwind-dev. 
b. enable CONFIG_DEBUG_FRAME in libunwind configuration: autoreconfig -i && 
./configure --enable-debug-frame
c. build libunwind and install it to /usr/lib/local
d. get kernel source by apt-get source linux and compile perf with 
following command:
 CFLAGS=-I/usr/local/include/ LDFLAGS="-lunwind -L/usr/local/lib/" make
e. perf call-graph works!

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libunwind-dev (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic aarch64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: arm64
  Date: Wed Jun  8 03:33:05 2016
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  SourcePackage: libunwind
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libunwind/+bug/1590236/+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

[Kernel-packages] [Bug 1590236] Re: perf --call-graph dwarf doesn't record correct call graph

2016-09-20 Thread Alberto Salvia Novella 
** Changed in: libunwind (Ubuntu Xenial)
   Importance: Undecided => High

** Changed in: linux (Ubuntu)
   Importance: Undecided => High

** Changed in: linux (Ubuntu Xenial)
   Importance: Undecided => High

** Changed in: libunwind (Ubuntu)
   Importance: Undecided => High

** Changed in: libunwind (Ubuntu Xenial)
   Status: New => Confirmed

** Changed in: linux (Ubuntu Xenial)
   Status: New => Confirmed

-- 
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/1590236

Title:
  perf --call-graph dwarf doesn't record correct call graph

Status in libunwind package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in libunwind source package in Xenial:
  Confirmed
Status in linux source package in Xenial:
  Confirmed

Bug description:
  1. What you expected to happen
  Profiling program by "perf --call-graph dwarf" shows correct call-graph in 
perf report

  2. What actually happened
  perf report doesn't show correct call graph. Then perf is re-builded from 
source. During building, perf configure detection says stock libunwind's 
debug_frame feature is not enabled. It leads perf can't record program's 
call-graph correctly.

  3. How it is solved on my local machine
a. get libunwind source by apt-get source libunwind-dev. 
b. enable CONFIG_DEBUG_FRAME in libunwind configuration: autoreconfig -i && 
./configure --enable-debug-frame
c. build libunwind and install it to /usr/lib/local
d. get kernel source by apt-get source linux and compile perf with 
following command:
 CFLAGS=-I/usr/local/include/ LDFLAGS="-lunwind -L/usr/local/lib/" make
e. perf call-graph works!

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libunwind-dev (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic aarch64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: arm64
  Date: Wed Jun  8 03:33:05 2016
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  SourcePackage: libunwind
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libunwind/+bug/1590236/+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

[Kernel-packages] [Bug 1590236] Re: perf --call-graph dwarf doesn't record correct call graph

2016-09-19 Thread Andy Whitcroft 
We may need to rebuild perf after libunwind is rebuilt.

-- 
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/1590236

Title:
  perf --call-graph dwarf doesn't record correct call graph

Status in libunwind package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in libunwind source package in Xenial:
  New
Status in linux source package in Xenial:
  New

Bug description:
  1. What you expected to happen
  Profiling program by "perf --call-graph dwarf" shows correct call-graph in 
perf report

  2. What actually happened
  perf report doesn't show correct call graph. Then perf is re-builded from 
source. During building, perf configure detection says stock libunwind's 
debug_frame feature is not enabled. It leads perf can't record program's 
call-graph correctly.

  3. How it is solved on my local machine
a. get libunwind source by apt-get source libunwind-dev. 
b. enable CONFIG_DEBUG_FRAME in libunwind configuration: autoreconfig -i && 
./configure --enable-debug-frame
c. build libunwind and install it to /usr/lib/local
d. get kernel source by apt-get source linux and compile perf with 
following command:
 CFLAGS=-I/usr/local/include/ LDFLAGS="-lunwind -L/usr/local/lib/" make
e. perf call-graph works!

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libunwind-dev (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic aarch64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: arm64
  Date: Wed Jun  8 03:33:05 2016
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  SourcePackage: libunwind
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libunwind/+bug/1590236/+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

[Kernel-packages] [Bug 1590236] Re: perf --call-graph dwarf doesn't record correct call graph

2016-09-19 Thread Matthias Klose 
** Also affects: libunwind (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Xenial)
   Importance: Undecided
   Status: New

-- 
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/1590236

Title:
  perf --call-graph dwarf doesn't record correct call graph

Status in libunwind package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in libunwind source package in Xenial:
  New
Status in linux source package in Xenial:
  New

Bug description:
  1. What you expected to happen
  Profiling program by "perf --call-graph dwarf" shows correct call-graph in 
perf report

  2. What actually happened
  perf report doesn't show correct call graph. Then perf is re-builded from 
source. During building, perf configure detection says stock libunwind's 
debug_frame feature is not enabled. It leads perf can't record program's 
call-graph correctly.

  3. How it is solved on my local machine
a. get libunwind source by apt-get source libunwind-dev. 
b. enable CONFIG_DEBUG_FRAME in libunwind configuration: autoreconfig -i && 
./configure --enable-debug-frame
c. build libunwind and install it to /usr/lib/local
d. get kernel source by apt-get source linux and compile perf with 
following command:
 CFLAGS=-I/usr/local/include/ LDFLAGS="-lunwind -L/usr/local/lib/" make
e. perf call-graph works!

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libunwind-dev (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic aarch64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: arm64
  Date: Wed Jun  8 03:33:05 2016
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  SourcePackage: libunwind
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libunwind/+bug/1590236/+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

[Kernel-packages] [Bug 1590236] Re: perf --call-graph dwarf doesn't record correct call graph

2016-09-19 Thread Launchpad Bug Tracker 
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: linux (Ubuntu)
   Status: New => Confirmed

-- 
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/1590236

Title:
  perf --call-graph dwarf doesn't record correct call graph

Status in libunwind package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  1. What you expected to happen
  Profiling program by "perf --call-graph dwarf" shows correct call-graph in 
perf report

  2. What actually happened
  perf report doesn't show correct call graph. Then perf is re-builded from 
source. During building, perf configure detection says stock libunwind's 
debug_frame feature is not enabled. It leads perf can't record program's 
call-graph correctly.

  3. How it is solved on my local machine
a. get libunwind source by apt-get source libunwind-dev. 
b. enable CONFIG_DEBUG_FRAME in libunwind configuration: autoreconfig -i && 
./configure --enable-debug-frame
c. build libunwind and install it to /usr/lib/local
d. get kernel source by apt-get source linux and compile perf with 
following command:
 CFLAGS=-I/usr/local/include/ LDFLAGS="-lunwind -L/usr/local/lib/" make
e. perf call-graph works!

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libunwind-dev (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic aarch64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: arm64
  Date: Wed Jun  8 03:33:05 2016
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  SourcePackage: libunwind
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libunwind/+bug/1590236/+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

[Kernel-packages] [Bug 1590236] Re: perf --call-graph dwarf doesn't record correct call graph

2016-09-19 Thread Brad Figg 
** Package changed: linux-meta (Ubuntu) => linux (Ubuntu)

** Changed in: linux (Ubuntu)
   Status: New => Confirmed

-- 
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/1590236

Title:
  perf --call-graph dwarf doesn't record correct call graph

Status in libunwind package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  1. What you expected to happen
  Profiling program by "perf --call-graph dwarf" shows correct call-graph in 
perf report

  2. What actually happened
  perf report doesn't show correct call graph. Then perf is re-builded from 
source. During building, perf configure detection says stock libunwind's 
debug_frame feature is not enabled. It leads perf can't record program's 
call-graph correctly.

  3. How it is solved on my local machine
a. get libunwind source by apt-get source libunwind-dev. 
b. enable CONFIG_DEBUG_FRAME in libunwind configuration: autoreconfig -i && 
./configure --enable-debug-frame
c. build libunwind and install it to /usr/lib/local
d. get kernel source by apt-get source linux and compile perf with 
following command:
 CFLAGS=-I/usr/local/include/ LDFLAGS="-lunwind -L/usr/local/lib/" make
e. perf call-graph works!

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libunwind-dev (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic aarch64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: arm64
  Date: Wed Jun  8 03:33:05 2016
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  SourcePackage: libunwind
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libunwind/+bug/1590236/+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

[Kernel-packages] [Bug 1590236] Re: perf --call-graph dwarf doesn't record correct call graph

2016-09-19 Thread Maxim Kuvyrkov 
Perf utility from linux-tools is affected for AArch64.

** Also affects: linux-meta (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  perf --call-graph dwarf doesn't record correct call graph

Status in libunwind package in Ubuntu:
  Confirmed
Status in linux-meta package in Ubuntu:
  New

Bug description:
  1. What you expected to happen
  Profiling program by "perf --call-graph dwarf" shows correct call-graph in 
perf report

  2. What actually happened
  perf report doesn't show correct call graph. Then perf is re-builded from 
source. During building, perf configure detection says stock libunwind's 
debug_frame feature is not enabled. It leads perf can't record program's 
call-graph correctly.

  3. How it is solved on my local machine
a. get libunwind source by apt-get source libunwind-dev. 
b. enable CONFIG_DEBUG_FRAME in libunwind configuration: autoreconfig -i && 
./configure --enable-debug-frame
c. build libunwind and install it to /usr/lib/local
d. get kernel source by apt-get source linux and compile perf with 
following command:
 CFLAGS=-I/usr/local/include/ LDFLAGS="-lunwind -L/usr/local/lib/" make
e. perf call-graph works!

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libunwind-dev (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic aarch64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: arm64
  Date: Wed Jun  8 03:33:05 2016
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  SourcePackage: libunwind
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libunwind/+bug/1590236/+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

[Kernel-packages] [Bug 1590236] Re: perf --call-graph dwarf doesn't record correct call graph

2016-09-19 Thread Maxim Kuvyrkov 
IMO, the AArch64 libunwind port (included via AArch64-port.diff debian
patch) should be setting enable_debug_frame to "yes" for aarch64
alongside arm in confirure.ac:

AC_MSG_CHECKING([whether to load .debug_frame sections])
AC_ARG_ENABLE(debug_frame,
AS_HELP_STRING([--enable-debug-frame],[Load the ".debug_frame" section if 
available]),, [
case "${target_arch}" in
  (arm) enable_debug_frame=yes;;
  (*)   enable_debug_frame=no;;
esac])
if test x$enable_debug_frame = xyes; then
  AC_DEFINE([CONFIG_DEBUG_FRAME], [], [Enable Debug Frame])
fi
AC_MSG_RESULT([$enable_debug_frame])

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

Title:
  perf --call-graph dwarf doesn't record correct call graph

Status in libunwind package in Ubuntu:
  Confirmed
Status in linux-meta package in Ubuntu:
  New

Bug description:
  1. What you expected to happen
  Profiling program by "perf --call-graph dwarf" shows correct call-graph in 
perf report

  2. What actually happened
  perf report doesn't show correct call graph. Then perf is re-builded from 
source. During building, perf configure detection says stock libunwind's 
debug_frame feature is not enabled. It leads perf can't record program's 
call-graph correctly.

  3. How it is solved on my local machine
a. get libunwind source by apt-get source libunwind-dev. 
b. enable CONFIG_DEBUG_FRAME in libunwind configuration: autoreconfig -i && 
./configure --enable-debug-frame
c. build libunwind and install it to /usr/lib/local
d. get kernel source by apt-get source linux and compile perf with 
following command:
 CFLAGS=-I/usr/local/include/ LDFLAGS="-lunwind -L/usr/local/lib/" make
e. perf call-graph works!

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libunwind-dev (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic aarch64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: arm64
  Date: Wed Jun  8 03:33:05 2016
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  SourcePackage: libunwind
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libunwind/+bug/1590236/+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