[Bug runtime/22582] SystemTap 3.2 stap script compilation error opt

["dsmith at redhat dot com" <sourceware-bugzilla@sourceware.org>]

https://sourceware.org/bugzilla/show_bug.cgi?id=22582

--- Comment #7 from David Smith <dsmith at redhat dot com> ---
(In reply to Gustavo Moreira from comment #6)

> 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?

Unfortunately, I have no idea. You'll just have to try them.

> 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

Those wiki pages were created by someone like you who was motivated to figure
out exactly what systemtap needed. I normally don't use self-built kernels, but
standard Fedora/RHEL distro kernels. I'm sure at the time that wiki page was
written that was a definitive list. But, things have changed (both on the
kernel side and the systemtap side).

As far as kernel config lines goes, it does depend on what kind of probing you
want to do. That list above looks fairly reasonable for kernel probing
(CONFIG_KPROBES being the main one). The wiki page lists several you are
missing, like: CONFIG_RELAY and CONFIG_DEBUG_FS.

Past that, it depends on what kinds of probes you want to use. CONFIG_UPROBES
is needed for userspace probing. CONFIG_NETFILTER is needed for netfilter.*
probes. CONFIG_TRACEPOINTS is needed for kernel.trace probes.
CONFIG_HAVE_HW_BREAKPOINT is needed for kernel.data probes.
CONFIG_HAVE_PERF_EVENTS and CONFIG_PERF_EVENTS are needed for perf.* probes.
CONFIG_PROC_FS is needed for procfs probes.

-- 
You are receiving this mail because:
You are the assignee for the bug.