This is the mail archive of the systemtap@sourceware.org mailing list for the systemtap project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

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


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.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]