From: "dsmith at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug server/15083] New: stapdyn needs system() support
Date: Wed, 30 Jan 2013 20:44:00 -0000 [thread overview]
Message-ID: <bug-15083-6586@http.sourceware.org/bugzilla/> (raw)
http://sourceware.org/bugzilla/show_bug.cgi?id=15083
Bug #: 15083
Summary: stapdyn needs system() support
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: server
AssignedTo: systemtap@sourceware.org
ReportedBy: dsmith@redhat.com
Depends on: 14491
Classification: Unclassified
Stapdyn needs support for the system() function, which allows users to execute
system commands in probes, like the following:
====
# stap -e 'probe begin { system("whoami"); exit() }'
dsmith
====
When you try this with dyninst, you get compilation errors:
====
stap --runtime=dyninst -e 'probe begin { system("whoami"); exit() }'
/tmp/stappmcBwb/stap_6e2d98d4dd508c0d340cf52b43604b2c_1111_src.c: In function
‘function_system’:
/tmp/stappmcBwb/stap_6e2d98d4dd508c0d340cf52b43604b2c_1111_src.c:112:2: error:
implicit declaration of function ‘_stp_ctl_send’
[-Werror=implicit-function-declaration]
_stp_ctl_send(STP_SYSTEM, STAP_ARG_cmd, strlen(STAP_ARG_cmd)+1);
^
cc1: all warnings being treated as errors
WARNING: gcc exited with status: 1
Pass 4: compilation failed. [man error::pass4]
====
(The fix here most likely depends on bug #14491.)
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2013-01-30 20:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-30 20:44 dsmith at redhat dot com [this message]
2013-04-26 17:19 ` [Bug server/15083] " dsmith at redhat dot com
2013-05-21 20:01 ` dsmith 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-15083-6586@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).