This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug translator/10799] global vs local variable confusion
- From: "mjw at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sources dot redhat dot com
- Date: 17 Oct 2009 14:16:41 -0000
- Subject: [Bug translator/10799] global vs local variable confusion
- References: <20091017112259.10799.mjw@redhat.com>
- Reply-to: sourceware-bugzilla at sourceware dot org
------- Additional Comments From mjw at redhat dot com 2009-10-17 14:16 -------
(In reply to comment #1)
> It's a namespace collision.
>
> We could warn against this by detecting if a probe alias variable
> could resolve to a global.
Yes, definitely. This issue is very surprising if you are probing aliases with
some wildcard. Depending on which aliases are matched your results could be
totally off when one of them happens to define a local variable that then resets
your global variables in your script.
--
http://sourceware.org/bugzilla/show_bug.cgi?id=10799
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.