From: "mysecondaccountabc at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug runtime/22582] SystemTap 3.2 stap script compilation error opt
Date: Wed, 13 Dec 2017 05:21:00 -0000 [thread overview]
Message-ID: <bug-22582-6586-eGEHqwR1fN@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-22582-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=22582
--- Comment #6 from Gustavo Moreira <mysecondaccountabc at gmail dot com> ---
(In reply to David Smith from comment #5)
> 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.
Yeah, it seems the syscall tracepoints are disabled.
# stap -l 'kernel.trace("sched_process_*")'
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_*")'
And unfortunately it seems this kernel version doesn't support syscall
tracepoints for ARM.
~/linux-3.2.93# grep -r HAVE_SYSCALL_TRACEPOINTS arch/*
arch/powerpc/Kconfig: select HAVE_SYSCALL_TRACEPOINTS
arch/s390/Kconfig: select HAVE_SYSCALL_TRACEPOINTS
arch/sh/Kconfig: select HAVE_SYSCALL_TRACEPOINTS
arch/sparc/Kconfig: select HAVE_SYSCALL_TRACEPOINTS
arch/x86/Kconfig: select HAVE_SYSCALL_TRACEPOINTS
Wonderful :S
So, let's start again. I will install everything from scratch using a fresh
Debian Jessie with kernel 3.16.0-4 and GCC 4.9.2. Should those be enough?
As per the kernel config features, what exactly does SystemTap need? That's a
bit confusing because different pages say different things. For instance, in
the official wiki for using systemtap with self-built kernels
[https://sourceware.org/systemtap/wiki/SystemTapWithSelfBuiltKernel], it
doesn't mention neither CONFIG_TRACEPOINTS nor CONFIG_HAVE_SYSCALL_TRACEPOINTS.
I know that would depend on what SystemTap features I will use but, let's say,
to have full support. Where can I find the most updated documentation about it?
I've gathered this list from different sources, should this be enough? Do you
recommend to add or remove something?
CONFIG_KPROBES=y
CONFIG_KPROBES_SANITY_TEST=n
CONFIG_KPROBE_EVENT=y
CONFIG_NET_DCCPPROBE=m
CONFIG_NET_SCTPPROBE=m
CONFIG_NET_TCPPROBE=y
CONFIG_DEBUG_INFO=y
CONFIG_DEBUG_INFO_REDUCED=n
CONFIG_ARM_KPROBES_TEST=n
CONFIG_TRACEPOINTS=y
CONFIG_HAVE_SYSCALL_TRACEPOINTS=y
Cheers,
Gus
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2017-12-13 5:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-11 8:13 [Bug runtime/22582] New: " mysecondaccountabc at gmail dot com
2017-12-11 14:18 ` [Bug runtime/22582] " dsmith at redhat dot com
2017-12-11 22:16 ` mysecondaccountabc at gmail dot com
2017-12-11 22:21 ` mysecondaccountabc at gmail dot com
2017-12-11 22:27 ` mysecondaccountabc at gmail dot com
2017-12-12 15:04 ` dsmith at redhat dot com
2017-12-13 5:21 ` mysecondaccountabc at gmail dot com [this message]
2017-12-13 18:47 ` dsmith at redhat dot com
2024-01-18 1:57 ` wcohen at redhat dot com
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-22582-6586-eGEHqwR1fN@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=systemtap@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).