Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1201320 > unrolled thread

[BUG] perf/script: segfault on simple command

Started byStephane Eranian <eranian@google.com>
First post2015-08-06 00:50 +0200
Last post2015-08-06 17:20 +0200
Articles 4 — 3 participants

Back to article view | Back to linux.kernel


Contents

  [BUG] perf/script: segfault on simple command Stephane Eranian <eranian@google.com> - 2015-08-06 00:50 +0200
    Re: [BUG] perf/script: segfault on simple command Jiri Olsa <jolsa@redhat.com> - 2015-08-06 07:50 +0200
      Re: [BUG] perf/script: segfault on simple command Arnaldo Carvalho de Melo <acme@redhat.com> - 2015-08-06 16:30 +0200
        Re: [BUG] perf/script: segfault on simple command Arnaldo Carvalho de Melo <acme@redhat.com> - 2015-08-06 17:20 +0200

#1201320 — [BUG] perf/script: segfault on simple command

FromStephane Eranian <eranian@google.com>
Date2015-08-06 00:50 +0200
Subject[BUG] perf/script: segfault on simple command
Message-ID<pUfFw-6J8-9@gated-at.bofh.it>
Hi Arnaldo, Jiri

Running this simple command from tip.git tree, I get:


$ perf record ls

[ perf record: Woken up 1 times to write data ]
[ perf record: Captured and wrote 0.011 MB perf.data (9 samples) ]

$ perf script
Segmentation fault (core dumped)

$ gdb perf
(gdb) r script

Program received signal SIGSEGV, Segmentation fault.
0x000000000050f98b in pevent_set_function_resolver (pevent=0x0,
func=0x4b2f50 <machine__resolve_kernel_addr>, priv=0x180bf98) at
event-parse.c:464
464 free(pevent->func_resolver);
(gdb) bt
#0  0x000000000050f98b in pevent_set_function_resolver (pevent=0x0,
func=0x4b2f50 <machine__resolve_kernel_addr>, priv=0x180bf98) at
event-parse.c:464
#1  0x000000000043cf2a in cmd_script (argc=0, argv=0x7fffffffe320,
prefix=<optimized out>) at builtin-script.c:1864
#2  0x0000000000474025 in run_builtin (p=p@entry=0x77a810
<commands+336>, argc=argc@entry=1, argv=argv@entry=0x7fffffffe320) at
perf.c:370
#3  0x000000000041cb50 in handle_internal_command
(argv=0x7fffffffe320, argc=1) at perf.c:429
#4  run_argv (argv=0x7fffffffe0a0, argcp=0x7fffffffe0ac) at perf.c:473
#5  main (argc=1, argv=0x7fffffffe320) at perf.c:588

Looks like something is fundamentally broken here.
Do you know what?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [next] | [standalone]


#1201444

FromJiri Olsa <jolsa@redhat.com>
Date2015-08-06 07:50 +0200
Message-ID<pUmdY-86Q-33@gated-at.bofh.it>
In reply to#1201320
On Wed, Aug 05, 2015 at 03:40:32PM -0700, Stephane Eranian wrote:
> Hi Arnaldo, Jiri
> 
> Running this simple command from tip.git tree, I get:
> 
> 
> $ perf record ls
> 
> [ perf record: Woken up 1 times to write data ]
> [ perf record: Captured and wrote 0.011 MB perf.data (9 samples) ]
> 
> $ perf script
> Segmentation fault (core dumped)
> 
> $ gdb perf
> (gdb) r script
> 
> Program received signal SIGSEGV, Segmentation fault.
> 0x000000000050f98b in pevent_set_function_resolver (pevent=0x0,
> func=0x4b2f50 <machine__resolve_kernel_addr>, priv=0x180bf98) at
> event-parse.c:464
> 464 free(pevent->func_resolver);
> (gdb) bt
> #0  0x000000000050f98b in pevent_set_function_resolver (pevent=0x0,
> func=0x4b2f50 <machine__resolve_kernel_addr>, priv=0x180bf98) at
> event-parse.c:464
> #1  0x000000000043cf2a in cmd_script (argc=0, argv=0x7fffffffe320,
> prefix=<optimized out>) at builtin-script.c:1864
> #2  0x0000000000474025 in run_builtin (p=p@entry=0x77a810
> <commands+336>, argc=argc@entry=1, argv=argv@entry=0x7fffffffe320) at
> perf.c:370
> #3  0x000000000041cb50 in handle_internal_command
> (argv=0x7fffffffe320, argc=1) at perf.c:429
> #4  run_argv (argv=0x7fffffffe0a0, argcp=0x7fffffffe0ac) at perf.c:473
> #5  main (argc=1, argv=0x7fffffffe320) at perf.c:588
> 
> Looks like something is fundamentally broken here.
> Do you know what?

hi,
yep, it should be already taken care of:
http://marc.info/?l=linux-kernel&m=143863009413104&w=2

jirka
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [prev] | [next] | [standalone]


#1201789

FromArnaldo Carvalho de Melo <acme@redhat.com>
Date2015-08-06 16:30 +0200
Message-ID<pUulc-367-29@gated-at.bofh.it>
In reply to#1201444
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)

> > $ gdb perf
> > (gdb) r script

> > Program received signal SIGSEGV, Segmentation fault.
> > 0x000000000050f98b in pevent_set_function_resolver (pevent=0x0,
> > func=0x4b2f50 <machine__resolve_kernel_addr>, priv=0x180bf98) at
> > event-parse.c:464
> > 464 free(pevent->func_resolver);
> > (gdb) bt
> > #0  0x000000000050f98b in pevent_set_function_resolver (pevent=0x0,
> > func=0x4b2f50 <machine__resolve_kernel_addr>, priv=0x180bf98) at

> > 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.

- Arnaldo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [prev] | [next] | [standalone]


#1201836

FromArnaldo Carvalho de Melo <acme@redhat.com>
Date2015-08-06 17:20 +0200
Message-ID<pUv7z-4og-1@gated-at.bofh.it>
In reply to#1201789
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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [prev] | [standalone]


Back to top | Article view | linux.kernel


csiph-web