Bug 2700 - make some parameters set run-time vs compile-time
Summary: make some parameters set run-time vs compile-time
Status: RESOLVED WONTFIX
Alias: None
Product: systemtap
Classification: Unclassified
Component: translator (show other bugs)
Version: unspecified
: P2 normal
Target Milestone: ---
Assignee: Unassigned
URL:
Keywords:
Depends on: 2208
Blocks:
  Show dependency tree / graph
 
Reported: 2006-05-26 00:51 UTC by Frank Ch. Eigler
Modified: 2015-12-04 15:27 UTC (History)
0 users

See Also:
Host:
Target:
Build:
Last reconfirmed:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Frank Ch. Eigler 2006-05-26 00:51:32 UTC 
Several parameters now set with "stap -DFOO=bar ..." turn into compile-time
macros/constants, and are not changeable at run time.  It would be nice to turn
some of them into special variables that show up as plain integers in C code,
and are changeable with module options.  This will be especially handy once we
have bug #2208 done.

Ordinary script globals already support initialization via module-params.  These
extra parameters would intrude on the same namespace, but that's OK.  For
backward compatibility, the "-DPARAM=value" could still function as an
initialization of the parameter.

examples:
MAXERRORS
MAXSKIPPED
MAXACTION
MAXMAPENTRIES

negative examples (i.e., these affect compile-time struct layout)
MAXSTRINGLEN
MAXNESTING
Comment 1 Frank Ch. Eigler 2015-12-04 15:27:31 UTC 
One might pursue some such things with special /*guru*/ tapset functions to clear counters instead.