From: "dsmith at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug translator/16914] probe syscall.* fails with compilation error
Date: Tue, 06 May 2014 20:44:00 -0000 [thread overview]
Message-ID: <bug-16914-6586-ZajEVDzjwm@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-16914-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=16914
David Smith <dsmith at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #9 from David Smith <dsmith at redhat dot com> ---
OK, I"ve got the systemtap problems fixed in commit 293523b. However, that
kernel doesn't have kprobes:
====
# stap -vp4 -e 'probe syscall.open { printf("hi\n") }'
Pass 1: parsed user script and 104 library script(s) using
149268virt/29880res/2940shr/27308data kb, in 380usr/10sys/399real ms.
Pass 2: analyzed script: 2 probe(s), 1 function(s), 40 embed(s), 0 global(s)
using 180248virt/61760res/3812shr/58288data kb, in 1440usr/160sys/1600real ms.
Pass 3: translated to C into
"/tmp/stapewvvDK/stap_62dcdbc1e584020a6a19f7cc43b29fdc_24567_src.c" using
180248virt/62096res/4148shr/58288data kb, in 20usr/110sys/136real ms.
/tmp/stapewvvDK/stap_62dcdbc1e584020a6a19f7cc43b29fdc_24567_src.c:1567:2:
error: #error "Need CONFIG_KPROBES!"
#error "Need CONFIG_KPROBES!"
^
make[1]: ***
[/tmp/stapewvvDK/stap_62dcdbc1e584020a6a19f7cc43b29fdc_24567_src.o] Error 1
make: *** [_module_/tmp/stapewvvDK] Error 2
WARNING: kbuild exited with status: 2
Pass 4: compiled C into "stap_62dcdbc1e584020a6a19f7cc43b29fdc_24567.ko" in
9880usr/1290sys/12392real ms.
Pass 4: compilation failed. [man error::pass4]
====
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2014-05-06 20:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-06 14:00 [Bug translator/16914] New: " mcermak at redhat dot com
2014-05-06 14:00 ` [Bug translator/16914] " mcermak at redhat dot com
2014-05-06 14:30 ` dsmith at redhat dot com
2014-05-06 17:46 ` mcermak at redhat dot com
2014-05-06 18:17 ` jistone at redhat dot com
2014-05-06 18:36 ` dsmith at redhat dot com
2014-05-06 19:42 ` mcermak at redhat dot com
2014-05-06 20:05 ` dsmith at redhat dot com
2014-05-06 20:23 ` mcermak at redhat dot com
2014-05-06 20:44 ` dsmith at redhat dot com [this message]
2015-02-12 16:36 ` aram.h at mgk dot ro
2015-02-12 17:34 ` dsmith at redhat dot com
2015-02-12 18:18 ` aram.h at mgk dot ro
2015-02-12 19:07 ` dsmith at redhat dot com
2015-02-12 21:10 ` aram.h at mgk dot ro
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-16914-6586-ZajEVDzjwm@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).