public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Ahern <dsahern@gmail.com>
To: Stephane Eranian <eranian@google.com>,
	LKML <linux-kernel@vger.kernel.org>
Cc: Jiri Olsa <jolsa@redhat.com>,
	Arnaldo Carvalho de Melo <acme@redhat.com>,
	Peter Zijlstra <peterz@infradead.org>,
	"mingo@elte.hu" <mingo@elte.hu>,
	Namhyung Kim <namhyung@kernel.org>,
	"ak@linux.intel.com" <ak@linux.intel.com>
Subject: Re: [BUG] perf mem: perf mem report fails in TUI mode
Date: Tue, 09 Dec 2014 22:18:17 -0700	[thread overview]
Message-ID: <5487D799.5060404@gmail.com> (raw)
In-Reply-To: <CABPqkBTLjQPymwDgNKdOshZimKQ0DGWaqm0gC8uFbwPK7vWrsA@mail.gmail.com>

On 12/9/14 9:15 PM, Stephane Eranian wrote:
> Hi,
>
> I was running a couple of tests with perf mem from tip.git and
> found that perf mem -t load rep was failing only in TUI mode.
> With --stdio, it works fine. I did a bit of investigation and found
> out that the TUI mode is failing because some symbol (kernel)
> is showing up with a huge (negative) size. I don't understand
> the connection between the TUI vs. tty browser and symbols.
>
> To reproduce:
>      $ perf mem -t load rec my_test_program
>      $ perf mem -t load rep
>      $ perf mem -t load rep --stdio
>
> Debugging with TUI is a pain, so I stopped.
>
> I have a patch to improve perf mem a bit but I'd like to get this problem
> fixed first.
>
> Maybe you have a idea of what's going on.

I usually avoid the TUI by not installing slang-devel.

But, trying out Linus' current tip (a0e4467726c - post 3.18) this seems 
to work fine:
     perf mem -t load rec ls
     perf mem -t load rep

But kernel version for the box is 3.16.6-203.fc20.x86_64.

David

  reply	other threads:[~2014-12-10  5:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-10  4:15 [BUG] perf mem: perf mem report fails in TUI mode Stephane Eranian
2014-12-10  5:18 ` David Ahern [this message]
2014-12-10 15:21   ` Stephane Eranian
2014-12-10 15:30 ` Jiri Olsa
2014-12-10 15:46   ` Stephane Eranian
2014-12-10 16:12     ` Jiri Olsa

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=5487D799.5060404@gmail.com \
    --to=dsahern@gmail.com \
    --cc=acme@redhat.com \
    --cc=ak@linux.intel.com \
    --cc=eranian@google.com \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=namhyung@kernel.org \
    --cc=peterz@infradead.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