From: David Ahern <daahern@cisco.com>
To: Thomas Renninger <trenn@suse.de>
Cc: Frederic Weisbecker <fweisbec@gmail.com>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
Ingo Molnar <mingo@elte.hu>,
linux-perf-users@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: perf timechart broken
Date: Fri, 14 Jan 2011 10:09:05 -0700 [thread overview]
Message-ID: <4D308331.6010106@cisco.com> (raw)
In-Reply-To: <201101141800.18913.trenn@suse.de>
On 01/14/11 10:00, Thomas Renninger wrote:
>> http://www.mail-archive.com/linux-perf-
> users@vger.kernel.org/msg00057.html
> Looks slightly different, the segfault should happen in:
> process_sample_event
> But looks very much related, possibly it has not been made/make with
> DEBUG=1
> and -O6 was added and the backtrace is not 100% correct?
perf was built with DEBUG=1; that's how I got the pretty backtrace
versus having the arguments optimized out. The cpu=6291457 is the
garbage causing the segfault (there are only 2 cores in the system).
6291457 = 0x600001. Perhaps a mask is missing?
David
>
> I still did not have time to send it out, will do so on Mo.
>
> Thomas
next prev parent reply other threads:[~2011-01-14 17:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-07 10:04 perf timechart broken Thomas Renninger
2011-01-07 12:33 ` Ingo Molnar
2011-01-11 1:36 ` Frederic Weisbecker
2011-01-11 8:55 ` Thomas Renninger
2011-01-11 11:49 ` Arnaldo Carvalho de Melo
2011-01-11 14:51 ` Arnaldo Carvalho de Melo
2011-01-14 16:49 ` Thomas Renninger
2011-01-14 17:37 ` Arnaldo Carvalho de Melo
2011-01-11 18:56 ` David Ahern
2011-01-14 17:00 ` Thomas Renninger
2011-01-14 17:09 ` David Ahern [this message]
2011-01-17 10:50 ` Thomas Renninger
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=4D308331.6010106@cisco.com \
--to=daahern@cisco.com \
--cc=acme@redhat.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=trenn@suse.de \
/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;
as well as URLs for NNTP newsgroup(s).