From: Ben Hutchings <ben@decadent.org.uk>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>,
Paul Mackerras <paulus@samba.org>, Ingo Molnar <mingo@elte.hu>,
Arnaldo Carvalho de Melo <acme@redhat.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Jonathan Nieder <jrnieder@gmail.com>,
604755@bugs.debian.org
Subject: [Fwd: Bug#604755: perf timechart: segfault in perf_session__process_events]
Date: Sun, 28 Nov 2010 21:35:50 +0000 [thread overview]
Message-ID: <1290980150.3292.356.camel@localhost> (raw)
[-- Attachment #1: Type: text/plain, Size: 2477 bytes --]
-------- Forwarded Message --------
From: Jonathan Nieder <jrnieder@gmail.com>
Reply-to: Jonathan Nieder <jrnieder@gmail.com>, 604755@bugs.debian.org
To: submit@bugs.debian.org
Subject: Bug#604755: perf timechart: segfault in perf_session__process_events
Date: Tue, 23 Nov 2010 21:59:45 -0600
Package: linux-tools-2.6.36
Version: 2.6.36-1~experimental.1
Tags: upstream
Can't seem to get "perf timechart" working.
$ uname -r
2.6.36-trunk-686
# perf timechart record echo hi
hi
[ perf record: Woken up 1 times to write data ]
[ perf record: Captured and wrote 0.079 MB perf.data (~3471 samples) ]
# chmod a+r perf.data
$ gdb --args perf_2.6.36 timechart
[...]
(gdb) run
Starting program: /usr/bin/perf_2.6.36 timechart
[Thread debugging using libthread_db enabled]
Program received signal SIGSEGV, Segmentation fault.
0x08061969 in ?? ()
(gdb) bt
#0 0x08061969 in ?? ()
#1 0x0808998e in ?? ()
#2 0x080888a6 in ?? ()
#3 0x080894b8 in __perf_session__process_events ()
#4 0x08089890 in perf_session__process_events ()
#5 0x08060041 in cmd_timechart ()
#6 0x0805210e in ?? ()
#7 0x080527cd in main ()
Also was reproducible with upstream linux and perf 2.6.37-rc3.
Valgrind trace (source line numbers refer to v2.6.37-rc3):
Invalid read of size 4
at 0x805B5C1: process_sample_event (builtin-timechart.c:505)
by 0x808654D: process_finished_round (session.c:410)
by 0x8085CF5: perf_session__process_event (session.c:633)
by 0x808732F: __perf_session__process_events (session.c:827)
by 0x80875CF: perf_session__process_events (session.c:867)
by 0x805BDE0: cmd_timechart (builtin-timechart.c:949)
by 0x804CCED: run_builtin (perf.c:286)
by 0x804D47E: main (perf.c:357)
Address 0x5416558 is 8 bytes after a block of size 72 alloc'd
at 0x4023F50: malloc (vg_replace_malloc.c:236)
by 0x8085EFA: perf_session__process_event (session.c:553)
by 0x808732F: __perf_session__process_events (session.c:827)
by 0x80875CF: perf_session__process_events (session.c:867)
by 0x805BDE0: cmd_timechart (builtin-timechart.c:949)
by 0x804CCED: run_builtin (perf.c:286)
by 0x804D47E: main (perf.c:357)
Is this a known problem? Where should it be reported?
(Ooh, this time it wrote a timechart before segfaulting! Apparently
v2.6.37-rc3 userspace + debian 2.6.36 kernel is the recipe for
success...)
Ciao,
Jonathan
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
reply other threads:[~2010-11-28 21:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1290980150.3292.356.camel@localhost \
--to=ben@decadent.org.uk \
--cc=604755@bugs.debian.org \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@redhat.com \
--cc=jrnieder@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulus@samba.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox