This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug runtime/22582] SystemTap 3.2 stap script compilation error opt
- From: "dsmith at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sourceware dot org
- Date: Tue, 12 Dec 2017 15:04:55 +0000
- Subject: [Bug runtime/22582] SystemTap 3.2 stap script compilation error opt
- Auto-submitted: auto-generated
- References: <bug-22582-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=22582
--- Comment #5 from David Smith <dsmith at redhat dot com> ---
I took a look at your attachments. Your
stapconf_1ddada75a347accc585e3d1a06438f1e_713.h file doesn't contain
STAPCONF_UTRACE_VIA_TRACEPOINTS. This means that your kernel doesn't support
the 5 tracepoints systemtap needs to do userspace tracing. They are:
sched_process_fork, sched_process_exit, sched_process_exec, sys_enter, and
sys_exit
You can check for these tracepoints via the following:
===
# stap -l 'kernel.trace("sched_process_*")'
kernel.trace("sched:sched_process_exec")
kernel.trace("sched:sched_process_exit")
kernel.trace("sched:sched_process_fork")
kernel.trace("sched:sched_process_free")
kernel.trace("sched:sched_process_wait")
# stap -l 'kernel.trace("sys_*")'
kernel.trace("raw_syscalls:sys_enter")
kernel.trace("raw_syscalls:sys_exit")
===
If the sys_enter/sys_exit tracepoints are missing, that would mean your kernel
doesn't have CONFIG_HAVE_SYSCALL_TRACEPOINTS.
--
You are receiving this mail because:
You are the assignee for the bug.