Summary: | optional $context variables | ||
---|---|---|---|
Product: | systemtap | Reporter: | Frank Ch. Eigler <fche> |
Component: | translator | Assignee: | Rajan Arora <rarora> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | prasad |
Priority: | P2 | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Host: | Target: | ||
Build: | Last reconfirmed: | ||
Attachments: | patch for review |
Description
Frank Ch. Eigler
2008-12-05 18:54:04 UTC
Such a functionality would help address name-space issues that might arise due to distinct variable names based on CONFIG_<>. Using a combination of '?' for function names and say $?var on variables, differences in kernel code based on CONFIG_<> option can be tolerated by the tapset/script. Created attachment 3808 [details]
patch for review
substitutes target symbol with literal 0 on enabling session level flag via
--ignore-context
I'd rename "--ignore-context" to "--skip-badvars" or somesuch and maybe tighten up the warning message, but otherwise looks great. A blurb in NEWS/stap.1.in and a test case would complete the job. commit 3bd0d4d |