All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@redhat.com>
To: Kirill Smelkov <kirr@mns.spb.ru>
Cc: Frederic Weisbecker <fweisbec@gmail.com>,
	Ingo Molnar <mingo@elte.hu>, Mike Galbraith <efault@gmx.de>,
	Paul Mackerras <paulus@samba.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Stephane Eranian <eranian@google.com>,
	Tom Zanussi <tzanussi@gmail.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [BUG] perf top -> annotate broken; bisected to 69aad6f1
Date: Tue, 11 Jan 2011 15:11:24 -0200	[thread overview]
Message-ID: <20110111171124.GB11968@ghostprotocols.net> (raw)
In-Reply-To: <20110111163520.GA4554@tugrik.mns.mnsspb.ru>

Em Tue, Jan 11, 2011 at 07:35:20PM +0300, Kirill Smelkov escreveu:
> Hello up there,
> 
> Since 69aad6f1ee69546dea8535ab8f3da9f445d57328 (perf tools: Introduce
> event selectors; Jan 3 2011) annotating a symbol in perf top segfaults:
> 
>     Program received signal SIGSEGV, Segmentation fault.
>     [Switching to Thread 0xb714cb90 (LWP 4662)]
>     event_name (evsel=0x0) at util/parse-events.c:274
>     274             return __event_name(type, config);
>     (gdb) bt
>     #0  event_name (evsel=0x0) at util/parse-events.c:274
>     #1  0x0805f892 in display_thread (arg=0x9422448) at builtin-top.c:359
>     #2  0xb77234c0 in start_thread () from /lib/i686/cmov/libpthread.so.0
>     #3  0xb732b84e in clone () from /lib/i686/cmov/libc.so.6
> 
> 
> It used to work...

Thanks for the report, working on a fix.

- Arnaldo

  reply	other threads:[~2011-01-11 17:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-11 16:35 [BUG] perf top -> annotate broken; bisected to 69aad6f1 Kirill Smelkov
2011-01-11 17:11 ` Arnaldo Carvalho de Melo [this message]
2011-01-11 17:23   ` Arnaldo Carvalho de Melo
2011-01-11 18:24     ` Kirill Smelkov

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=20110111171124.GB11968@ghostprotocols.net \
    --to=acme@redhat.com \
    --cc=efault@gmx.de \
    --cc=eranian@google.com \
    --cc=fweisbec@gmail.com \
    --cc=kirr@mns.spb.ru \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=paulus@samba.org \
    --cc=peterz@infradead.org \
    --cc=tzanussi@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.