linux-kernel - [BUG] perf/script: segfault on simple command

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <CABPqkBTur8JDh86ep-1Et0ygrS_1v5nqwi207sL6p1U9pcCcKQ@mail.gmail.com>
Date:	Wed, 5 Aug 2015 15:40:32 -0700
From:	Stephane Eranian <eranian@...gle.com>
To:	LKML <linux-kernel@...r.kernel.org>
Cc:	Arnaldo Carvalho de Melo <acme@...hat.com>,
	Jiri Olsa <jolsa@...hat.com>,
	Peter Zijlstra <peterz@...radead.org>,
	"mingo@...e.hu" <mingo@...e.hu>,
	Namhyung Kim <namhyung@...nel.org>,
	Adrian Hunter <adrian.hunter@...el.com>
Subject: [BUG] perf/script: segfault on simple command

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@...ry=0x77a810
<commands+336>, argc=argc@...ry=1, argv=argv@...ry=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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/