From: "dsmith at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug runtime/22582] SystemTap 3.2 stap script compilation error opt
Date: Mon, 11 Dec 2017 14:18:00 -0000 [thread overview]
Message-ID: <bug-22582-6586-o9rlvEh4BW@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-22582-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=22582
David Smith <dsmith at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |WAITING
Last reconfirmed| |2017-12-11
CC| |dsmith at redhat dot com
Ever confirmed|0 |1
--- Comment #1 from David Smith <dsmith at redhat dot com> ---
(In reply to Gustavo Moreira from comment #0)
> I'm having the following compilation error compiling a stap script in ARM
> with SystemTap 3.2:
>
> $ sudo stap -v -g -p4 -DSTP_NO_OVERLOAD systemtap-strace.stp -m stap_trace
> Compiling systemtap module ...
> ./systemtap-strace.stp -> ./stap_trace.ko
> Pass 1: parsed user script and 452 library scripts using
> 35092virt/26404res/2260shr/24360data kb, in 4950usr/190sys/5187real ms.
> Pass 2: analyzed script: 734 probes, 230 functions, 104 embeds, 63 globals
> using 68040virt/60300res/3180shr/57308data kb, in
> 2348300usr/36720sys/2415777real ms.
> Pass 3: translated to C into "/tmp/stapBqLAih/stap_trace_src.c" using
> 68040virt/60492res/3412shr/57308data kb, in 121940usr/440sys/124281real ms.
> /tmp/stapBqLAih/stap_trace_src.c:198942:28: error: field ‘ops’ has
> incomplete type
> /tmp/stapBqLAih/stap_trace_src.c: In function ‘systemtap_module_init’:
> /tmp/stapBqLAih/stap_trace_src.c:199900:9: error: implicit declaration of
> function ‘stap_utrace_detach_ops’ [-Werror=implicit-function-declaration]
> cc1: all warnings being treated as errors
Interesting. The task_finder functionality (part of the user-space tracing),
needs for several kernel tracepoints to exist. If they don't exist, you should
have either gotten a compile error or they should have semi-gracefully just
refused to work.
Is CONFIG_TRACEPOINTS set in your custom kernel?
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2017-12-11 14:18 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 ` dsmith at redhat dot com [this message]
2017-12-11 22:16 ` [Bug runtime/22582] " 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
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-o9rlvEh4BW@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).