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]

Re: Using kernel global variables


Frank Ch. Eigler wrote:
Mike Mason <mmlnx@us.ibm.com> writes:

I believe the variable must be within the *scope* of the probed
function. The function doesn't necessarily have to use the variable
for it to be within scope. A global defined in the same file as the
function is automatically within scope.

Or even *declared* in the same compilation unit - that should work too.


I don't think exported symbols are within a function's scope from
SystemTap's perspective [...]

We could change things to search for globals in other compilation units too - exported ones first, static ones next (with the obvious risk of name collisions).

- FChE
If we could specify that the variable was global it would eliminate the chance of name collision.


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