linux-kernel - [BUG] perf timechart 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: <CALkWK0k5sQ9WCGevFQ3D18=Fs3ziS8imVVvasE0QR9e0r91cYA@mail.gmail.com>
Date:	Wed, 2 Oct 2013 16:36:45 +0530
From:	Ramkumar Ramachandra <artagnon@...il.com>
To:	LKML <linux-kernel@...r.kernel.org>
Cc:	Ingo Molnar <mingo@...nel.org>,
	Arnaldo Carvalho de Melo <acme@...stprotocols.net>,
	Jiri Olsa <jolsa@...hat.com>
Subject: [BUG] perf timechart segfault

Hi,

I tried using the `perf timechart` command after a `sudo perf
timechart record -- git status`, and it segfaulted. Backtrace follows:

Program received signal SIGSEGV, Segmentation fault.
0x0000000000000000 in ?? ()
(gdb) bt
#0  0x0000000000000000 in ?? ()
#1  0x000000000047d728 in perf_session_deliver_event
(session=session@...ry=0x8ea450, event=event@...ry=0x7ffff7f13f98,
    sample=sample@...ry=0x7fffffffd530,
tool=tool@...ry=0x7fffffffd7a0, file_offset=file_offset@...ry=8088)
    at util/session.c:1006
#2  0x000000000047faec in perf_session__process_event
(file_offset=8088, tool=0x7fffffffd7a0, event=0x7ffff7f13f98,
    session=0x8ea450) at util/session.c:1098
#3  __perf_session__process_events (session=session@...ry=0x8ea450,
data_offset=<optimized out>,
    data_size=<optimized out>, file_size=635384,
tool=tool@...ry=0x7fffffffd7a0) at util/session.c:1360
#4  0x000000000047ff81 in perf_session__process_events
(self=self@...ry=0x8ea450, tool=tool@...ry=0x7fffffffd7a0)
    at util/session.c:1403
#5  0x000000000042f12a in __cmd_timechart (output_name=0x4ee399
"output.svg") at builtin-timechart.c:1009
#6  cmd_timechart (argc=0, argv=0x7fffffffdf20, prefix=<optimized
out>) at builtin-timechart.c:1116
#7  0x0000000000419925 in run_builtin (p=p@...ry=0x725f90
<commands+240>, argc=argc@...ry=1,
    argv=argv@...ry=0x7fffffffdf20) at perf.c:319
#8  0x0000000000419199 in handle_internal_command
(argv=0x7fffffffdf20, argc=1) at perf.c:376
#9  run_argv (argv=0x7fffffffdd20, argcp=0x7fffffffdd2c) at perf.c:420
#10 main (argc=1, argv=0x7fffffffdf20) at perf.c:521

I compiled it with EXTRA_CFLAGS="-O0 -g", so all the debugging symbols
should be available. Not sure what's going on, or why I needed sudo to
record data in the first place.

Any hints?
--
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/