This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
Re: Using kernel global variables
- From: Mike Mason <mmlnx at us dot ibm dot com>
- To: David Wilder <dwilder at us dot ibm dot com>
- Cc: SystemTAP <systemtap at sources dot redhat dot com>
- Date: Sun, 05 Aug 2007 10:50:00 -0700
- Subject: Re: Using kernel global variables
- References: <46B35E2C.6000907@us.ibm.com>
David Wilder wrote:
It is my understanding if we want to access a kernel global variable in
a tap script we must be in a context that is using the variable.
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.
I don't think exported symbols are within a function's scope from SystemTap's perspective, though the function can see them. Perhaps the dwarf info doesn't allow for that.
Mike