From: Arnaldo Carvalho de Melo <acme@infradead.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org, David Ahern <dsahern@gmail.com>,
Frederic Weisbecker <fweisbec@gmail.com>,
Mike Galbraith <efault@gmx.de>, Paul Mackerras <paulus@samba.org>,
Peter Zijlstra <peterz@infradead.org>,
Stephane Eranian <eranian@google.com>
Subject: Re: [GIT PULL 0/6] perf/core fixes and improvements
Date: Fri, 14 Oct 2011 12:07:53 -0300 [thread overview]
Message-ID: <20111014150753.GA19655@ghostprotocols.net> (raw)
In-Reply-To: <20111014071610.GA20648@elte.hu>
Em Fri, Oct 14, 2011 at 09:16:10AM +0200, Ingo Molnar escreveu:
> Hm, got a segfault with a plain 'perf top' on a 3.0-0.rc7.git3-ish
> box:
>
> ./perf top
> Segmentation fault (core dumped)
>
> It took about 20 attempts to reproduce the segfault, and it always
> occured right after the first refresh (which, unlike the working
> cases showed zero samples):
>
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread 0x7ffff13a3700 (LWP 21657)]
> ui_browser__hists_seek (whence=<optimized out>, offset=0,
> self=0x7fffec0008c0)
> at util/ui/browsers/hists.c:682
> 682 h->row_offset = 0;
> (gdb)
>
> (gdb) bt
> #0 ui_browser__hists_seek (whence=<optimized out>, offset=0, self=0x7fffec0008c0)
browser->top was NULL at that point, it was only being initialized in
the refresh routine, fixed in my tree, please re-pull.
One can easily trigger it by specifying a seldom ocurring event, which
will start the browser without samples, then generating such event, I
used net:netif_rx + ping on my workstation.
> Btw., a side note: could we try to reset the console on segfaults and
> similar crashes? TUI crashes tend to leave the console in a messed up
> (blue, etc.) state.
I'll work on that, and also on allowing changing the browser colors,
say, to look like the stdio one.
- Arnaldo
next prev parent reply other threads:[~2011-10-14 15:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-13 15:08 [GIT PULL 0/6] perf/core fixes and improvements Arnaldo Carvalho de Melo
2011-10-13 15:08 ` [PATCH 1/6] perf hists browser: Recalculate browser pointers after resort/decay Arnaldo Carvalho de Melo
2011-10-13 15:08 ` [PATCH 2/6] perf hists: Don't free decayed entries if in the annotation browser Arnaldo Carvalho de Melo
2011-10-13 15:08 ` [PATCH 3/6] perf hists: Fix compilation when NO_NEWT_SUPPORT is set Arnaldo Carvalho de Melo
2011-10-13 15:08 ` [PATCH 4/6] perf ui browser: Handle SIGWINCH Arnaldo Carvalho de Melo
2011-10-13 15:08 ` [PATCH 5/6] perf ui browser: Remove ui_browser__add_exit_keys Arnaldo Carvalho de Melo
2011-10-13 15:08 ` [PATCH 6/6] perf top: Remove entries from entries_collapsed on decay Arnaldo Carvalho de Melo
2011-10-14 7:16 ` [GIT PULL 0/6] perf/core fixes and improvements Ingo Molnar
2011-10-14 15:07 ` Arnaldo Carvalho de Melo [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-08-16 14:41 Arnaldo Carvalho de Melo
2011-08-17 21:36 ` Ingo Molnar
2011-08-18 12:43 ` Arnaldo Carvalho de Melo
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=20111014150753.GA19655@ghostprotocols.net \
--to=acme@infradead.org \
--cc=dsahern@gmail.com \
--cc=efault@gmx.de \
--cc=eranian@google.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulus@samba.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;
as well as URLs for NNTP newsgroup(s).