From: "David S. Ahern" <daahern@cisco.com>
To: linux-perf-users@vger.kernel.org
Subject: perf timechart: segfault in c_state_end
Date: Wed, 08 Dec 2010 17:56:04 -0700 [thread overview]
Message-ID: <4D002924.9060504@cisco.com> (raw)
'perf timechart' is segfaulting.
Latest perf-core.git: commit c277443cfc29b1623b4923219ff0bdb48b91b589
(gdb) set args timechart -i /tmp/perf-tc.data
(gdb) run
Starting program: /tmp/build-perf/perf timechart -i /tmp/perf-tc.data
[Thread debugging using libthread_db enabled]
Detaching after fork from child process 23900.
Program received signal SIGSEGV, Segmentation fault.
0x0000000000417199 in c_state_end (cpu=6291457,
timestamp=30181412965584) at builtin-timechart.c:364
364 pwr->state = cpus_cstate_state[cpu];
(gdb) bt
#0 0x0000000000417199 in c_state_end (cpu=6291457,
timestamp=30181412965584)
at builtin-timechart.c:364
#1 0x0000000000417832 in process_sample_event (event=0x7ffff7f467e8,
sample=0x7fffffffdb30,
session=0xba3990) at builtin-timechart.c:505
#2 0x0000000000447096 in perf_session_deliver_event (session=0xba3990,
event=0x7ffff7f467e8,
sample=0x7fffffffdb30, ops=0x741560) at util/session.c:675
#3 0x0000000000446a26 in flush_sample_queue (s=0xba3990, ops=0x741560)
at util/session.c:487
#4 0x0000000000446b32 in process_finished_round (event=0x7ffff7f557c0,
session=0xba3990,
ops=0x741560) at util/session.c:545
#5 0x000000000044748e in perf_session__process_event (session=0xba3990,
event=0x7ffff7f557c0,
ops=0x741560, file_offset=128960) at util/session.c:757
#6 0x0000000000447cac in __perf_session__process_events
(session=0xba3990, data_offset=1160,
data_size=669144, file_size=670304, ops=0x741560) at util/session.c:968
#7 0x0000000000447f14 in perf_session__process_events (self=0xba3990,
ops=0x741560)
at util/session.c:1038
#8 0x0000000000418935 in __cmd_timechart () at builtin-timechart.c:949
#9 0x0000000000418bcf in cmd_timechart (argc=0, argv=0x7fffffffe150,
prefix=0x0)
at builtin-timechart.c:1044
(gdb) print {struct sample_data} 0x7fffffffdb30
$1 = {ip = 18446744071579611228, pid = 0, tid = 0, time =
30181412965584, addr = 5210168, id = 50,
stream_id = 17768320, period = 16, cpu = 0, raw_size = 28, raw_data =
0x7ffff7f4681c,
callchain = 0xbb248679b4370ba3}
(gdb) print {struct power_entry} 0x7ffff7f4681c
$2 = {te = {type = 326, flags = 4 '\004', preempt_count = 0 '\000', pid
= 0, lock_depth = -1},
type = 0, value = 38654705664, cpu_id = 9298719120581197825}
reply other threads:[~2010-12-09 0:56 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=4D002924.9060504@cisco.com \
--to=daahern@cisco.com \
--cc=linux-perf-users@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.