linux-kernel - [BUG] perf script segfault

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: <5519D376.6010509@gmail.com>
Date:	Mon, 30 Mar 2015 16:51:34 -0600
From:	David Ahern <dsahern@...il.com>
To:	Arnaldo Carvalho de Melo <acme@...nel.org>,
	Stephane Eranian <eranian@...gle.com>,
	Jiri Olsa <jolsa@...nel.org>
CC:	LKML <linux-kernel@...r.kernel.org>
Subject: [BUG] perf script segfault

Surprised Stephane has not hit this one yet:

$ perf record -e <any-event> -a | perf script
Segmentation fault (core dumped)

It's the second one that core dumps.

$ gdb perf core.16704
...
[New LWP 16704]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Core was generated by `/tmp/perf/perf script'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  perf_tool__fill_defaults (tool=tool@...ry=0x0) at util/session.c:259
259		if (tool->sample == NULL)
...
(gdb) bt
#0  perf_tool__fill_defaults (tool=tool@...ry=0x0) at util/session.c:259
#1  0x00000000004a5baa in __perf_session__process_pipe_events 
(session=0x2178b80) at util/session.c:1178
#2  perf_session__process_events (session=0x2178b80) at util/session.c:1416
#3  0x000000000043c5dc in __cmd_script (script=0x7fffc7a4d840) at 
builtin-script.c:803
#4  cmd_script (argc=<optimized out>, argv=<optimized out>, 
prefix=<optimized out>) at builtin-script.c:1840
...

tool was moved to ordered_events and is not initialized for pipe mode. I 
don't have time to look into it more than that before PTO on Wednesday.

David
--
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/