From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <systemtap-return-14702-listarch-systemtap=sources.redhat.com@sourceware.org>
Received: (qmail 7826 invoked by alias); 16 Dec 2009 11:39:30 -0000
Received: (qmail 7678 invoked by uid 48); 16 Dec 2009 11:39:15 -0000
Date: Wed, 16 Dec 2009 11:39:00 -0000
From: "mjw at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Message-ID: <20091216113915.11096.mjw@redhat.com>
Reply-To: sourceware-bugzilla@sourceware.org
Subject: [Bug translator/11096] New: Getting global module vars in functions
X-Bugzilla-Reason: AssignedTo
Mailing-List: contact systemtap-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <systemtap.sourceware.org>
List-Subscribe: <mailto:systemtap-subscribe@sourceware.org>
List-Post: <mailto:systemtap@sourceware.org>
List-Help: <mailto:systemtap-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: systemtap-owner@sourceware.org
X-SW-Source: 2009-q4/txt/msg00943.txt.bz2

It is often convenient to grab a global variable value in a function. But
currently you cannot do that, so you have to grab it in a probe handler and
store it globally or pass it to the function invocation (then you can use the
address of this variable and @cast(var "struct", "module") to extract the
information in the function).

Possible syntax: @global($var, "module")

-- 
           Summary: Getting global module vars in functions
           Product: systemtap
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: translator
        AssignedTo: systemtap at sources dot redhat dot com
        ReportedBy: mjw at redhat dot com


http://sourceware.org/bugzilla/show_bug.cgi?id=11096

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.