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 translator/19110] New: make it easier to know if the kernel exports a particular function


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.


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