Bug 1866 - MAXACTION exceeded ERROR information when tested in heavy system load
Summary: MAXACTION exceeded ERROR information when tested in heavy system load
Status: RESOLVED DUPLICATE of bug 1884
Alias: None
Product: systemtap
Classification: Unclassified
Component: translator (show other bugs)
Version: unspecified
: P2 normal
Target Milestone: ---
Assignee: Martin Hunt
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-11-15 10:38 UTC by bibo,mao
Modified: 2005-11-30 11:25 UTC (History)
2 users (show)

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 bibo,mao 2005-11-15 10:38:49 UTC 
When test pfaults.stp in heavy systemload in IA32 and EM64T platform, there 
will be some error information and then stap process will exit abnormally. And 
the error information is:
  ERROR: MAXACTION exceeded near identifier 'print' at pfaults.stp:44:5
And I in function report() of this script, there is a foreach loop sentence, in 
this function it will exceed max value MAXACTION(1000)
Comment 1 Frank Ch. Eigler 2005-11-16 13:38:16 UTC 
The translator is working as designed.  The lookup tables must have grown too
large to iterate through completely within a probe.  pfaults.stp could be
changed to strictly limit its own activities, such as exiting the foreach()
after some smaller number of iterations.  Or it could be run with a MAXACTION
parameter adjustment ("stap -DMAXACTION=2000 pfaults.stp").
Comment 2 Martin Hunt 2005-11-30 11:25:37 UTC 

*** This bug has been marked as a duplicate of 1884 ***