On Fri, Feb 16, 2018 at 10:25:31AM +0800, Jin, Yao wrote:
SNIP
> > From my opinion, the option '--max-stack' in perf report looks not very
> > necessary. While it's just my personal opinion, need to hear from more
> > people. :)
> >
> > Thanks
> > Jin Yao
> >
> > > thanks,
> > > jirka
> > >
>
On 2/13/2018 10:00 PM, Jin, Yao wrote:
On 2/13/2018 5:45 PM, Jiri Olsa wrote:
On Tue, Feb 13, 2018 at 04:44:28PM +0800, Jin Yao wrote:
Following command lines will cause perf crash.
perf record -j call -g -a
perf report --branch-history
*** Error in `perf': double free or corruption (!pr
On 2/13/2018 5:45 PM, Jiri Olsa wrote:
On Tue, Feb 13, 2018 at 04:44:28PM +0800, Jin Yao wrote:
Following command lines will cause perf crash.
perf record -j call -g -a
perf report --branch-history
*** Error in `perf': double free or corruption (!prev): 0x104aa040 ***
=== Backtr
On Tue, Feb 13, 2018 at 04:44:28PM +0800, Jin Yao wrote:
> Following command lines will cause perf crash.
>
> perf record -j call -g -a
> perf report --branch-history
>
> *** Error in `perf': double free or corruption (!prev): 0x104aa040 ***
> === Backtrace: =
> /lib/x86_64-l
Following command lines will cause perf crash.
perf record -j call -g -a
perf report --branch-history
*** Error in `perf': double free or corruption (!prev): 0x104aa040 ***
=== Backtrace: =
/lib/x86_64-linux-gnu/libc.so.6(+0x77725)[0x7f6b37254725]
/lib/x86_64-linux-gnu/libc.s
5 matches
Mail list logo