From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 120330 invoked by alias); 13 Dec 2017 18:47:44 -0000 Mailing-List: contact systemtap-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: systemtap-owner@sourceware.org Received: (qmail 120252 invoked by uid 48); 13 Dec 2017 18:47:40 -0000 From: "dsmith at redhat dot com" To: systemtap@sourceware.org Subject: [Bug runtime/22582] SystemTap 3.2 stap script compilation error opt Date: Wed, 13 Dec 2017 18:47:00 -0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: systemtap X-Bugzilla-Component: runtime X-Bugzilla-Version: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: dsmith at redhat dot com X-Bugzilla-Status: WAITING X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: systemtap at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2017-q4/txt/msg00197.txt.bz2 https://sourceware.org/bugzilla/show_bug.cgi?id=3D22582 --- Comment #7 from David Smith --- (In reply to Gustavo Moreira from comment #6) > So, let's start again. I will install everything from scratch using a fre= sh > 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 instanc= e, > 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 SystemT= ap > features I will use but, let's say, to have full support. Where can I find > the most updated documentation about it? >=20 > I've gathered this list from different sources, should this be enough? Do > you recommend to add or remove something? >=20 > CONFIG_KPROBES=3Dy > CONFIG_KPROBES_SANITY_TEST=3Dn > CONFIG_KPROBE_EVENT=3Dy > CONFIG_NET_DCCPPROBE=3Dm > CONFIG_NET_SCTPPROBE=3Dm > CONFIG_NET_TCPPROBE=3Dy > CONFIG_DEBUG_INFO=3Dy > CONFIG_DEBUG_INFO_REDUCED=3Dn > CONFIG_ARM_KPROBES_TEST=3Dn > CONFIG_TRACEPOINTS=3Dy > CONFIG_HAVE_SYSCALL_TRACEPOINTS=3Dy Those wiki pages were created by someone like you who was motivated to figu= re 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_UPROB= ES 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. --=20 You are receiving this mail because: You are the assignee for the bug.