From: David Ahern <dsahern@gmail.com>
To: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>
Cc: Jiri Olsa <jolsa@kernel.org>, Namhyung Kim <namhyung@kernel.org>,
Stephane Eranian <eranian@google.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [BUG] segfault in perf-top -- thread refcnt
Date: Fri, 27 Mar 2015 14:13:26 -0600 [thread overview]
Message-ID: <5515B9E6.5020007@gmail.com> (raw)
In-Reply-To: <20150327201126.GM21510@kernel.org>
On 3/27/15 2:11 PM, Arnaldo Carvalho de Melo wrote:
> Em Fri, Mar 27, 2015 at 11:31:22AM -0600, David Ahern escreveu:
>> >Hi Arnaldo:
>> >
>> >If I leave 'perf top -z' running it eventually crashes with the backtrace in
>> >the new thread refcnt code:
> Humm, tried here with:
>
> perf top -d 1 -z
>
> I.e. as you, with the --tui, and also with --stdio, so far couldn't
> reproduce.
>
2 things:
1. let run for a long time. go about using the server. do lots of
builds, etc. it takes time
2. use a box with a LOT of cpus (1024 in my case)
Make sure ulimit is set to get the core.
next prev parent reply other threads:[~2015-03-27 20:13 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-27 17:31 [BUG] segfault in perf-top -- thread refcnt David Ahern
2015-03-27 19:51 ` Arnaldo Carvalho de Melo
2015-03-27 20:11 ` Arnaldo Carvalho de Melo
2015-03-27 20:13 ` David Ahern [this message]
2015-03-30 8:07 ` Jiri Olsa
2015-03-30 10:22 ` Jiri Olsa
2015-03-30 11:21 ` Jiri Olsa
2015-03-30 11:49 ` Jiri Olsa
2015-03-30 12:48 ` Namhyung Kim
2015-03-30 12:56 ` Jiri Olsa
2015-03-30 13:06 ` Namhyung Kim
2015-03-30 14:02 ` Arnaldo Carvalho de Melo
2015-03-31 0:15 ` Namhyung Kim
2015-03-30 13:07 ` Arnaldo Carvalho de Melo
2015-03-30 13:20 ` Jiri Olsa
2015-03-30 13:59 ` Arnaldo Carvalho de Melo
2015-03-30 14:58 ` Arnaldo Carvalho de Melo
2015-03-30 15:13 ` Arnaldo Carvalho de Melo
2015-03-31 0:27 ` Namhyung Kim
2015-03-31 0:46 ` Arnaldo Carvalho de Melo
2015-03-31 7:21 ` Namhyung Kim
2015-03-30 13:22 ` Arnaldo Carvalho de Melo
2015-03-30 13:09 ` Arnaldo Carvalho de Melo
2015-03-30 13:17 ` Arnaldo Carvalho de Melo
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=5515B9E6.5020007@gmail.com \
--to=dsahern@gmail.com \
--cc=arnaldo.melo@gmail.com \
--cc=eranian@google.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=namhyung@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 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).