linux-kernel - Re: [PATCH 2/8] perf, tools: Support handling complete branch stacks as histograms v4

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: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20140307131928.GA13974@krava.brq.redhat.com>
Date:	Fri, 7 Mar 2014 14:19:28 +0100
From:	Jiri Olsa <jolsa@...hat.com>
To:	Andi Kleen <ak@...ux.intel.com>
Cc:	Andi Kleen <andi@...stfloor.org>, acme@...hat.com,
	mingo@...nel.org, linux-kernel@...r.kernel.org, eranian@...gle.com,
	namhyung@...nel.org
Subject: Re: [PATCH 2/8] perf, tools: Support handling complete branch stacks
 as histograms v4

On Wed, Mar 05, 2014 at 07:31:49AM -0800, Andi Kleen wrote:
> > segfaults here..
> > 
> > [jolsa@...va perf]$ ./perf record -g sleep 1
> > [ perf record: Woken up 1 times to write data ]
> > [ perf record: Captured and wrote 0.013 MB perf.data (~567 samples) ]
> > [jolsa@...va perf]$ ./perf report
> > perf: Segmentation fault
> > [jolsa@...va perf]$ 
> 
> Thanks. Fixed with this patch:
> 
> commit 124014960a8fb09043914fb79ea86e0444408ab0
> Author: Andi Kleen <ak@...ux.intel.com>
> Date:   Wed Mar 5 07:28:56 2014 -0800
> 
>     perf, tools, report: Fix perf report without -b
>     
>     Fix report crash when -b is not used. Reported by Jiri Olsa.
>     
>     Signed-off-by: Andi Kleen <ak@...ux.intel.com>

you need to merge it with the original one,
so we dont have broken build.. git bisect wise

same for the gtk stuff

jirka
--
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/