This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
Re: Accessing user-space global variables in timer.profile?
- From: agentzh <agentzh at gmail dot com>
- To: Josh Stone <jistone at redhat dot com>
- Cc: David Smith <dsmith at redhat dot com>, systemtap at sourceware dot org
- Date: Fri, 7 Jun 2013 18:19:59 -0500
- Subject: Re: Accessing user-space global variables in timer.profile?
- References: <CAB4Tn6OYi=Vx19H4BLojphuuvjSp2drjvJFd3HxzAGj7=yD5cA at mail dot gmail dot com> <51755D3D dot 6020004 at redhat dot com> <CAB4Tn6OubWF71F9b3hNqXo85h96sr1Rp77-NmZAjmLPt=vAzyA at mail dot gmail dot com> <5175E28B dot 9050500 at redhat dot com> <CAB4Tn6ORHjkv+CuAN90Ju+gKEohSyNvpdvoq-fEsEEdUgAzjgg at mail dot gmail dot com> <51AD1B9A dot 3050907 at redhat dot com> <51AD24EB dot 5000708 at redhat dot com>
Hello Josh!
On Mon, Jun 3, 2013 at 6:21 PM, Josh Stone <jistone@redhat.com> wrote:
> Ugh, now it occurs to me that this suggestion only makes sense for @var
> globals, where there's a cu_name and no module name. For plain
> @var("name") it could be a local variable, and this really does need to
> be processed on the spot in dwarf_var_expanding_visitor.
>
Yeah, it makes sense :)
> Here's a possible outline to accomplish that with separate atvar_op:
>
[...]
>
> Hope I'm not over-engineering this... what do you think?
Thank you for your suggestions! They look good to me. I'll rewrite my
patch in the next few days accordingly :)
Thanks!
-agentzh