This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
RE: MAXACTION exceeded error while using systemtap
- From: "Stone, Joshua I" <joshua dot i dot stone at intel dot com>
- To: "Hien Nguyen" <hien at us dot ibm dot com>, "Frank Ch. Eigler" <fche at redhat dot com>
- Cc: "SystemTAP" <systemtap at sources dot redhat dot com>
- Date: Tue, 6 Dec 2005 12:41:22 -0800
- Subject: RE: MAXACTION exceeded error while using systemtap
Hien Nguyen wrote:
> Try to reset MAXACTION once in a while with this
>
> function reset_maxaction () %{
> if (CONTEXT && CONTEXT->actioncount)
> CONTEXT->actioncount=0;
> %}
>
> OR try to start your script with -DMAXACTION=<somehugenumber>
To me, both of these solutions are really just workarounds for what will
likely be a common problem. The first requires guru-mode, which should
not be necessary for a simple reporting script. The second is better,
though cumbersome.
Frank Ch. Eigler wrote:
> See http://sourceware.org/bugzilla/show_bug.cgi?id=1866
This bug was dismissed as being "behavior as designed" - but I think it
is worth questioning the design. Do we expect this to be a common
problem? If so, we need to find a way to make it less painful...
At the very least, we should have something along the Dtrace's printa():
http://docs.sun.com/app/docs/doc/817-6223/6mlkidlhv?a=view#chp-fmt-print
a
Their printa() only deals with aggregations (stats), but we really need
something like this for general arrays as well.
Bug #1121 seems applicable to this problem - is there any work being
done here?
http://sourceware.org/bugzilla/show_bug.cgi?id=1121
Josh