From: Jiri Olsa <jolsa@redhat.com>
To: Adrian Hunter <adrian.hunter@intel.com>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: perf seg fault
Date: Tue, 12 May 2020 17:10:43 +0200 [thread overview]
Message-ID: <20200512151043.GC3158213@krava> (raw)
In-Reply-To: <0517775a-3e0f-f900-4687-069d115077bd@intel.com>
On Tue, May 12, 2020 at 05:58:29PM +0300, Adrian Hunter wrote:
> Forgot to cc mailing list
>
> On 12/05/20 5:50 pm, Adrian Hunter wrote:
> > Hi
> >
> > I am getting a seg fault from your perf/core branch, as follows:
> >
> > # perf record uname
> > Linux
> > [ perf record: Woken up 1 times to write data ]
> > [ perf record: Captured and wrote 0.005 MB perf.data (7 samples) ]
> > perf: Segmentation fault
> > Obtained 6 stack frames.
> > [0x4e75b4]
> > [0x5d1ad0]
> > [0x5c9860]
> > [0x4a6e5c]
> > [0x5cb39b]
> > [0x76c89f]
> > Segmentation fault
> >
> > It goes away with --no-bpf-event:
> >
> > # perf record --no-bpf-event uname
> > Linux
> > [ perf record: Woken up 1 times to write data ]
> > [ perf record: Captured and wrote 0.005 MB perf.data (7 samples) ]
> > #
> >
> > kernel is from the same branch
> >
> > # uname -a
> > Linux buildroot 5.7.0-rc2-00028-g0fdddf5a583a #165 SMP Tue May 12 16:27:53
> > EEST 2020 x86_64 GNU/Linux
> >
> > # perf version --build-options
> > perf version 5.6.g0fdddf5a583a
> > dwarf: [ OFF ] # HAVE_DWARF_SUPPORT
> > dwarf_getlocations: [ OFF ] # HAVE_DWARF_GETLOCATIONS_SUPPORT
> > glibc: [ on ] # HAVE_GLIBC_SUPPORT
> > gtk2: [ OFF ] # HAVE_GTK2_SUPPORT
> > syscall_table: [ on ] # HAVE_SYSCALL_TABLE_SUPPORT
> > libbfd: [ on ] # HAVE_LIBBFD_SUPPORT
> > libelf: [ on ] # HAVE_LIBELF_SUPPORT
> > libnuma: [ OFF ] # HAVE_LIBNUMA_SUPPORT
> > numa_num_possible_cpus: [ OFF ] # HAVE_LIBNUMA_SUPPORT
> > libperl: [ OFF ] # HAVE_LIBPERL_SUPPORT
> > libpython: [ OFF ] # HAVE_LIBPYTHON_SUPPORT
> > libslang: [ on ] # HAVE_SLANG_SUPPORT
> > libcrypto: [ on ] # HAVE_LIBCRYPTO_SUPPORT
> > libunwind: [ OFF ] # HAVE_LIBUNWIND_SUPPORT
> > libdw-dwarf-unwind: [ OFF ] # HAVE_DWARF_SUPPORT
> > zlib: [ OFF ] # HAVE_ZLIB_SUPPORT
> > lzma: [ OFF ] # HAVE_LZMA_SUPPORT
> > get_cpuid: [ on ] # HAVE_AUXTRACE_SUPPORT
> > bpf: [ OFF ] # HAVE_LIBBPF_SUPPORT
> > aio: [ on ] # HAVE_AIO_SUPPORT
> > zstd: [ OFF ] # HAVE_ZSTD_SUPPORT
> >
> >
> > Any thoughts?
hum, I don't see that, do you reproduce with DEBUG=1?
to get more verbose backtrace
jirka
next prev parent reply other threads:[~2020-05-12 15:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <0cad7834-07b4-ec2f-13b5-d6a10b21ce48@intel.com>
2020-05-12 14:58 ` perf seg fault Adrian Hunter
2020-05-12 15:10 ` Jiri Olsa [this message]
2020-05-12 15:41 ` Arnaldo Carvalho de Melo
2020-05-12 15:45 ` Adrian Hunter
2020-05-12 15:55 ` Jiri Olsa
2020-05-12 16:17 ` Adrian Hunter
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=20200512151043.GC3158213@krava \
--to=jolsa@redhat.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=linux-kernel@vger.kernel.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 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.