All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jiri Olsa <jolsa@redhat.com>
To: Anthony LaTorre <tlatorre9@gmail.com>
Cc: peterz@infradead.org, mingo@redhat.com, jolsa@kernel.org,
	acme@kernel.org, alexander.shishkin@linux.intel.com,
	namhyung@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: perf report segfault
Date: Tue, 9 Oct 2018 23:38:00 +0200	[thread overview]
Message-ID: <20181009213800.GA31206@krava> (raw)
In-Reply-To: <CAO49af+zxxVh9HGfjKxS=vQcD5po7-oLU87Zp0F21M-C64nWUA@mail.gmail.com>

On Tue, Oct 09, 2018 at 01:54:48PM -0500, Anthony LaTorre wrote:
> Can you reproduce the segfault from the perf.data file I provided?

nope, but if it's dwarf callchain related I'd need perf archive
output to reproduce.. please run:

---
  $ perf record ...
  $ perf archive
  Now please run:

  $ tar xvf perf.data.tar.bz2 -C ~/.debug

  wherever you need to run 'perf report' on.
  $
---

and send/publish both perf.data and perf.data.tar.bz2 files

thanks,
jirka

      parent reply	other threads:[~2018-10-09 21:38 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAO49afLqUGuBi_R7BKyojqnkHrMGqXquy-FdVFscOu6Ez0cVFw@mail.gmail.com>
2018-10-09 16:47 ` perf report segfault Jiri Olsa
2018-10-09 18:54   ` Anthony LaTorre
2018-10-09 20:18     ` Anthony LaTorre
2018-10-09 21:41       ` Jiri Olsa
     [not found]         ` <CAO49af+5TaWrdYeM3XyHoti0obH--0txq9_a6_9ZPMuB-J=hjg@mail.gmail.com>
2018-10-09 22:19           ` Anthony LaTorre
2018-10-09 22:20           ` Jiri Olsa
2018-10-10  5:43             ` Sandipan Das
2018-10-10  6:19               ` Ingo Molnar
2018-10-10  7:14               ` Jiri Olsa
2018-10-10 12:54             ` Arnaldo Carvalho de Melo
2018-10-09 21:38     ` Jiri Olsa [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=20181009213800.GA31206@krava \
    --to=jolsa@redhat.com \
    --cc=acme@kernel.org \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=jolsa@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=peterz@infradead.org \
    --cc=tlatorre9@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.