lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CABPqkBThUvnJLcddd8Uik_Ssk-a6wojrB6rVCvg-Stzg2Bk+6A@mail.gmail.com>
Date:	Wed, 10 Dec 2014 10:46:59 -0500
From:	Stephane Eranian <eranian@...gle.com>
To:	Jiri Olsa <jolsa@...hat.com>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	Arnaldo Carvalho de Melo <acme@...hat.com>,
	Peter Zijlstra <peterz@...radead.org>,
	"mingo@...e.hu" <mingo@...e.hu>,
	Namhyung Kim <namhyung@...nel.org>,
	David Ahern <dsahern@...il.com>,
	"ak@...ux.intel.com" <ak@...ux.intel.com>
Subject: Re: [BUG] perf mem: perf mem report fails in TUI mode

On Wed, Dec 10, 2014 at 10:30 AM, Jiri Olsa <jolsa@...hat.com> wrote:
> On Tue, Dec 09, 2014 at 11:15:13PM -0500, 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
>
> hi,
> I couldn't reproduce any failure on the acme's perf/core
>
What about tip.git?

> since you indicated it's data dependent, could you share
> your perf.data?
>
I can send it to you directly.

> thanks,
> jirka
>
>>
>> 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.
>>
>> Thanks.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ