From: "jistone at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug tapsets/13721] local variable name collision
Date: Wed, 29 Feb 2012 03:02:00 -0000 [thread overview]
Message-ID: <bug-13721-6586-3RJlAVU8bh@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-13721-6586@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=13721
--- Comment #6 from Josh Stone <jistone at redhat dot com> 2012-02-29 03:02:38 UTC ---
I discovered that bug #10799 and commit 2e526da intended to solve (or at least
notify about) this very issue. However, the testcase here was failing on the
arity mismatch before this warning was ever checked. I just pushed commit
2a7153bf to reorder this, so now you'll get a "WARNING: cross-file global
variable reference" at least before the arity stuff.
The idea of reduced global scope may be as simple as turning that warning into
an error, although that would also make cross-tapset access fail. (Do we
care?)
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next prev parent reply other threads:[~2012-02-29 3:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-21 21:03 [Bug tapsets/13721] New: " dsmith at redhat dot com
2012-02-21 22:31 ` [Bug tapsets/13721] " jistone at redhat dot com
2012-02-21 22:37 ` jistone at redhat dot com
2012-02-23 15:46 ` dsmith at redhat dot com
2012-02-23 17:18 ` jistone at redhat dot com
2012-02-23 18:29 ` dsmith at redhat dot com
2012-02-29 3:02 ` jistone at redhat dot com [this message]
2015-11-11 9:44 ` mcermak at redhat dot com
2015-11-11 12:16 ` mcermak at redhat dot com
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-13721-6586-3RJlAVU8bh@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=systemtap@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).