Re: [BUG] segfault in perf-top -- thread refcnt

From: Jiri Olsa
Date: Mon Mar 30 2015 - 04:07:53 EST


On Fri, Mar 27, 2015 at 02:13:26PM -0600, David Ahern wrote:
> 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.

reproduced under 24 cpu box with kernel build (make -j25)
running on background.. will try to look closer

perf: Segmentation fault
-------- backtrace --------
./perf[0x4fd79b]
/lib64/libc.so.6(+0x358f0)[0x7f9cbff528f0]
./perf(thread__put+0x5b)[0x4b1a7b]
./perf(hists__delete_entries+0x70)[0x4c8670]
./perf[0x436a88]
./perf[0x4fa73d]
./perf(perf_evlist__tui_browse_hists+0x97)[0x4fc437]
./perf[0x4381d0]
/lib64/libpthread.so.0(+0x7ee5)[0x7f9cc1ff2ee5]
/lib64/libc.so.6(clone+0x6d)[0x7f9cc0011b8d]
[0x0]


jirka
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/