Public bug reported:
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)
** Affects: libunwind (Ubuntu)
Importance: Undecided
Status: New
** Tags: apport-bug arm64 xenial
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libunwind 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:
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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
