[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#638938: marked as done (linux-tools-3.0.0: "perf report" segfaults when using binary version; compiling from source works)

Your message dated Tue, 23 Aug 2011 09:22:57 -0700
with message-id <CAFoXKmqJWCredZZoiM_CXrf7qJnf8A6NrA601hiZuu-0LAh_3A@mail.gmail.com>
and subject line linux-tools-3.0.0: "perf report" segfaults when using binary version; compiling from source works
has caused the Debian Bug report #638938,
regarding linux-tools-3.0.0: "perf report" segfaults when using binary version; compiling from source works
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
638938: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=638938
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: linux-tools-3.0.0
Version: 3.0.0-1
Severity: normal


I captured a few perf traces on a live system (using "perf record --event cpu-clock --freq 1000 -a --output=mylog.perf").

When I try to run a report on those perf logs, it segfaults.  I can run it under gdb and get a stacktrace (below).

If I install the linux-source package, expand it, and do a "make" in tools/perf, then that version of perf works (no segfault).

The version I built does reference different shared libraries (according to ldd).  Most notably, it include libbfd-2.21.52-system.20110606.so.  I believe that cplus_demangle is only called if bfd is not present(?)


Stacktrace from gdb:

Program received signal SIGSEGV, Segmentation fault.
0x000000000047630f in ?? ()
(gdb) bt
#0  0x000000000047630f in ?? ()
#1  0x0000000000477be3 in ?? ()
#2  0x00000000004765d9 in ?? ()
#3  0x00000000004752f6 in ?? ()
#4  0x00000000004776e5 in ?? ()
#5  0x0000000000473e8a in ?? ()
#6  0x00000000004742e7 in ?? ()
#7  0x0000000000479f67 in cplus_demangle_print_callback ()
#8  0x000000000047a0d6 in ?? ()
#9  0x000000000047a267 in ?? ()
#10 0x000000000047a41e in cplus_demangle_v3 ()
#11 0x000000000046e778 in cplus_demangle ()
#12 0x000000000043f308 in ?? ()
#13 0x00000000004413db in dso__load ()
#14 0x0000000000449db0 in map__load ()
#15 0x0000000000449f0d in map__find_symbol ()
#16 0x000000000042ed7d in perf_event__preprocess_sample ()
#17 0x0000000000419fed in ?? ()
#18 0x000000000044c585 in ?? ()
#19 0x000000000044dbb3 in __perf_session__process_events ()
#20 0x000000000041a3c5 in cmd_report ()
#21 0x0000000000410a59 in _start ()


-- System Information:
Debian Release: wheezy/sid
 APT prefers testing
 APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.0.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages linux-tools-3.0.0 depends on:
ii  libc6                        2.13-16     Embedded GNU C Library: Shared lib
ii  libelf1                      0.152-1     library to read and write ELF file
ii  libnewt0.52                  0.52.11-2.1 Not Erik's Windowing Toolkit - tex
ii  libperl5.12                  5.12.4-4    shared Perl library
ii  libpython2.6                 2.6.7-3     Shared Python runtime library (ver
ii  libslang2                    2.2.4-2     S-Lang programming library - runti
ii  perl                         5.12.4-4    Larry Wall's Practical Extraction
ii  python                       2.6.7-3     interactive high-level object-orie

Versions of packages linux-tools-3.0.0 recommends:
ii  linux-base                    3.3        Linux image base package

Versions of packages linux-tools-3.0.0 suggests:
pn  linux-doc-3.0.0               <none>     (no description available)

-- no debconf information


--- End Message ---
--- Begin Message --- 
Version: 3.0.0-2

Thanks for the suggestions.  I tried manually installing 3.0.0-2 and
that did fix the problem (and going back to 3.0.0-1 did reintroduce
the problem).  The problem also was fixed when I compiled with
HAVE_CPLUS_DEMANGLE=YesPlease (and that was indeed linked without
libbfd).

I agree that this does likely point to a bugfix in a newer version of
a statically linked library, probably binutils-dev.

Thanks for the fix, and the help.  Closing, as this is fixed in 3.0.0-2.

Justin

--- End Message ---
Reply to: