public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@redhat.com>
To: Jiri Olsa <jolsa@redhat.com>
Cc: Stephane Eranian <eranian@google.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@kernel.org>,
	Namhyung Kim <namhyung@kernel.org>,
	Adrian Hunter <adrian.hunter@intel.com>
Subject: Re: [BUG] perf/script: segfault on simple command
Date: Thu, 6 Aug 2015 11:38:33 -0300	[thread overview]
Message-ID: <20150806143833.GB2265@redhat.com> (raw)
In-Reply-To: <20150806142829.GA2265@redhat.com>

Em Thu, Aug 06, 2015 at 11:28:29AM -0300, Arnaldo Carvalho de Melo escreveu:
> Em Thu, Aug 06, 2015 at 07:41:20AM +0200, Jiri Olsa escreveu:
> > On Wed, Aug 05, 2015 at 03:40:32PM -0700, Stephane Eranian wrote:
> > > $ perf script
> > > Segmentation fault (core dumped)
> 
> > > event-parse.c:464
> > > Looks like something is fundamentally broken here.
> > > Do you know what?
> 
> > yep, it should be already taken care of:
> > http://marc.info/?l=linux-kernel&m=143863009413104&w=2
> 
> Yeah, pushed already to Ingo, should land in tip.git soon.

Yeah, its there already:

https://git.kernel.org/cgit/linux/kernel/git/tip/tip.git/log/

Has it as:

"perf script: No tracepoints? Don't call libtraceevent."

https://git.kernel.org/cgit/linux/kernel/git/tip/tip.git/commit/?id=9ee67421fe3b67a0796d6ea620fd5fcb037d3f89

- Arnaldo

      reply	other threads:[~2015-08-06 15:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-05 22:40 [BUG] perf/script: segfault on simple command Stephane Eranian
2015-08-06  5:41 ` Jiri Olsa
2015-08-06 14:28   ` Arnaldo Carvalho de Melo
2015-08-06 14:38     ` Arnaldo Carvalho de Melo [this message]

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=20150806143833.GB2265@redhat.com \
    --to=acme@redhat.com \
    --cc=adrian.hunter@intel.com \
    --cc=eranian@google.com \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=namhyung@kernel.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