From: "dsmith at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug translator/19110] New: make it easier to know if the kernel exports a particular function
Date: Fri, 09 Oct 2015 18:30:00 -0000 [thread overview]
Message-ID: <bug-19110-6586@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=19110
Bug ID: 19110
Summary: make it easier to know if the kernel exports a
particular function
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: translator
Assignee: systemtap at sourceware dot org
Reporter: dsmith at redhat dot com
Target Milestone: ---
When working on bug #6525, I needed to know whether a certain kernel function
is exported or not. Currently, the way you do this is by adding a new
'exportconf' test in the translator source, which requires recompiling the
translator.
I wonder if we could somehow handle this differently, so that recompiling the
translator isn't required. For runtime C code use, a brute force approach would
be to just add a #define for everything that is exported:
#define STAPCONF_FOO_EXPORTED
#define STAPCONF_BAR_EXPORTED
etc.
For bonus points, we could provide a preprocessor directive, perhaps something
like:
%(exported("foo") %?
...
%)
Although off the top of my head I can't really think of a use for knowing if a
kernel function is exported in systemtap script code.
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2015-10-09 18:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-09 18:30 dsmith at redhat dot com [this message]
2024-02-21 13:04 ` [Bug translator/19110] " fche 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-19110-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).