* module("*") wildcard expansion problem
@ 2006-07-31 3:25 Mike Mason
2006-07-31 14:46 ` David Smith
0 siblings, 1 reply; 3+ messages in thread
From: Mike Mason @ 2006-07-31 3:25 UTC (permalink / raw)
To: systemtap
I noticed that the following line in the current.stp test:
module("*").function("*interrupt*")
expands to every function in modules and the kernel with "interrupt" in
its name. I assume it should only expand to functions in modules, correct?
Mike Mason
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: module("*") wildcard expansion problem
2006-07-31 3:25 module("*") wildcard expansion problem Mike Mason
@ 2006-07-31 14:46 ` David Smith
0 siblings, 0 replies; 3+ messages in thread
From: David Smith @ 2006-07-31 14:46 UTC (permalink / raw)
To: Mike Mason; +Cc: systemtap
On Sun, 2006-07-30 at 20:25 -0700, Mike Mason wrote:
> I noticed that the following line in the current.stp test:
>
> module("*").function("*interrupt*")
>
> expands to every function in modules and the kernel with "interrupt" in
> its name. I assume it should only expand to functions in modules, correct?
>
> Mike Mason
Mike,
That certainly doesn't look correct to me. Please file a bugzilla on
this problem and I'll look into it.
--
David Smith
dsmith@redhat.com
Red Hat, Inc.
http://www.redhat.com
256.217.0141 (direct)
256.837.0057 (fax)
^ permalink raw reply [flat|nested] 3+ messages in thread
* RE: module("*") wildcard expansion problem
@ 2006-07-31 17:09 Stone, Joshua I
0 siblings, 0 replies; 3+ messages in thread
From: Stone, Joshua I @ 2006-07-31 17:09 UTC (permalink / raw)
To: David Smith, Mike Mason; +Cc: systemtap
On Monday, July 31, 2006 7:44 AM, David Smith wrote:
> On Sun, 2006-07-30 at 20:25 -0700, Mike Mason wrote:
>> I noticed that the following line in the current.stp test:
>>
>> module("*").function("*interrupt*")
>>
>> expands to every function in modules and the kernel with "interrupt"
>> in its name. I assume it should only expand to functions in modules,
>> correct?
>
> That certainly doesn't look correct to me. Please file a bugzilla on
> this problem and I'll look into it.
I believe the current parser treats the kernel as a module named
"kernel". That is, kernel.function(...) is equivalent to
module("kernel").function(...).
I'm not saying that's the way it should be, just that this is the
current behavior...
Josh
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2006-07-31 17:09 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2006-07-31 3:25 module("*") wildcard expansion problem Mike Mason
2006-07-31 14:46 ` David Smith
2006-07-31 17:09 Stone, Joshua I
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).