类 Profiler

  • 所有已实现的接口:
    DebugEventListener

    public class Profiler
    extends BlankDebugEventListener
    Using the debug event interface, track what is happening in the parser and record statistics about the runtime.
    • 字段详细资料

      • DATA_SEP

        public static final java.lang.String DATA_SEP
        另请参阅:
        常量字段值
      • newline

        public static final java.lang.String newline
      • Version

        public static final java.lang.String Version
        Because I may change the stats, I need to track that for later computations to be consistent.
        另请参阅:
        常量字段值
      • RUNTIME_STATS_FILENAME

        public static final java.lang.String RUNTIME_STATS_FILENAME
        另请参阅:
        常量字段值
      • parser

        public DebugParser parser
        Ack, should not store parser; can't do remote stuff. Well, we pass input stream around too so I guess it's ok.
      • ruleLevel

        protected int ruleLevel
      • lastRealTokenTouchedInDecision

        protected Token lastRealTokenTouchedInDecision
      • uniqueRules

        protected java.util.Set<java.lang.String> uniqueRules
      • currentGrammarFileName

        protected java.util.Stack<java.lang.String> currentGrammarFileName
      • currentRuleName

        protected java.util.Stack<java.lang.String> currentRuleName
      • currentLine

        protected java.util.Stack<java.lang.Integer> currentLine
      • currentPos

        protected java.util.Stack<java.lang.Integer> currentPos
      • backtrackDepth

        protected int backtrackDepth
    • 构造器详细资料

      • Profiler

        public Profiler()
    • 方法详细资料

      • enterRule

        public void enterRule​(java.lang.String grammarFileName,
                              java.lang.String ruleName)
        从接口复制的说明: DebugEventListener
        The parser has just entered a rule. No decision has been made about which alt is predicted. This is fired AFTER init actions have been executed. Attributes are defined and available etc... The grammarFileName allows composite grammars to jump around among multiple grammar files.
        指定者:
        enterRule 在接口中 DebugEventListener
        覆盖:
        enterRule 在类中 BlankDebugEventListener
      • exitRule

        public void exitRule​(java.lang.String grammarFileName,
                             java.lang.String ruleName)
        从接口复制的说明: DebugEventListener
        This is the last thing executed before leaving a rule. It is executed even if an exception is thrown. This is triggered after error reporting and recovery have occurred (unless the exception is not caught in this rule). This implies an "exitAlt" event. The grammarFileName allows composite grammars to jump around among multiple grammar files.
        指定者:
        exitRule 在接口中 DebugEventListener
        覆盖:
        exitRule 在类中 BlankDebugEventListener
      • examineRuleMemoization

        public void examineRuleMemoization​(IntStream input,
                                           int ruleIndex,
                                           int stopIndex,
                                           java.lang.String ruleName)
        Track memoization; this is not part of standard debug interface but is triggered by profiling. Code gen inserts an override for this method in the recognizer, which triggers this method. Called from alreadyParsedRule().
      • memoize

        public void memoize​(IntStream input,
                            int ruleIndex,
                            int ruleStartIndex,
                            java.lang.String ruleName)
        Warning: doesn't track success/failure, just unique recording event
      • location

        public void location​(int line,
                             int pos)
        从接口复制的说明: DebugEventListener
        To watch a parser move through the grammar, the parser needs to inform the debugger what line/charPos it is passing in the grammar. For now, this does not know how to switch from one grammar to the other and back for island grammars etc... This should also allow breakpoints because the debugger can stop the parser whenever it hits this line/pos.
        指定者:
        location 在接口中 DebugEventListener
        覆盖:
        location 在类中 BlankDebugEventListener
      • enterDecision

        public void enterDecision​(int decisionNumber,
                                  boolean couldBacktrack)
        从接口复制的说明: DebugEventListener
        Every decision, fixed k or arbitrary, has an enter/exit event so that a GUI can easily track what LT/consume events are associated with prediction. You will see a single enter/exit subrule but multiple enter/exit decision events, one for each loop iteration.
        指定者:
        enterDecision 在接口中 DebugEventListener
        覆盖:
        enterDecision 在类中 BlankDebugEventListener
      • inDecision

        public boolean inDecision()
        The parser is in a decision if the decision depth > 0. This works for backtracking also, which can have nested decisions.
      • beginBacktrack

        public void beginBacktrack​(int level)
        Track backtracking decisions. You'll see a fixed or cyclic decision and then a backtrack. enter rule ... enter decision LA and possibly consumes (for cyclic DFAs) begin backtrack level mark m rewind m end backtrack level, success exit decision ... exit rule
        指定者:
        beginBacktrack 在接口中 DebugEventListener
        覆盖:
        beginBacktrack 在类中 BlankDebugEventListener
      • rewind

        public void rewind​(int i)
        从接口复制的说明: DebugEventListener
        After an arbitrairly long lookahead as with a cyclic DFA (or with any backtrack), this informs the debugger that stream should be rewound to the position associated with marker.
        指定者:
        rewind 在接口中 DebugEventListener
        覆盖:
        rewind 在类中 BlankDebugEventListener
      • rewind

        public void rewind()
        从接口复制的说明: DebugEventListener
        Rewind to the input position of the last marker. Used currently only after a cyclic DFA and just before starting a sem/syn predicate to get the input position back to the start of the decision. Do not "pop" the marker off the state. mark(i) and rewind(i) should balance still.
        指定者:
        rewind 在接口中 DebugEventListener
        覆盖:
        rewind 在类中 BlankDebugEventListener
      • recognitionException

        public void recognitionException​(RecognitionException e)
        从接口复制的说明: DebugEventListener
        A recognition exception occurred such as NoViableAltException. I made this a generic event so that I can alter the exception hierachy later without having to alter all the debug objects. Upon error, the stack of enter rule/subrule must be properly unwound. If no viable alt occurs it is within an enter/exit decision, which also must be rewound. Even the rewind for each mark must be unwount. In the Java target this is pretty easy using try/finally, if a bit ugly in the generated code. The rewind is generated in DFA.predict() actually so no code needs to be generated for that. For languages w/o this "finally" feature (C++?), the target implementor will have to build an event stack or something. Across a socket for remote debugging, only the RecognitionException data fields are transmitted. The token object or whatever that caused the problem was the last object referenced by LT. The immediately preceding LT event should hold the unexpected Token or char. Here is a sample event trace for grammar: b : C ({;}A|B) // {;} is there to prevent A|B becoming a set | D ; The sequence for this rule (with no viable alt in the subrule) for input 'c c' (there are 3 tokens) is: commence LT(1) enterRule b location 7 1 enter decision 3 LT(1) exit decision 3 enterAlt1 location 7 5 LT(1) consumeToken [c/<4>,1:0] location 7 7 enterSubRule 2 enter decision 2 LT(1) LT(1) recognitionException NoViableAltException 2 1 2 exit decision 2 exitSubRule 2 beginResync LT(1) consumeToken [c/<4>,1:1] LT(1) endResync LT(-1) exitRule b terminate
        指定者:
        recognitionException 在接口中 DebugEventListener
        覆盖:
        recognitionException 在类中 BlankDebugEventListener
      • terminate

        public void terminate()
        从接口复制的说明: DebugEventListener
        Parsing is over; successfully or not. Mostly useful for telling remote debugging listeners that it's time to quit. When the rule invocation level goes to zero at the end of a rule, we are done parsing.
        指定者:
        terminate 在接口中 DebugEventListener
        覆盖:
        terminate 在类中 BlankDebugEventListener
      • setParser

        public void setParser​(DebugParser parser)
      • toNotifyString

        public java.lang.String toNotifyString()
      • toString

        public java.lang.String toString()
        覆盖:
        toString 在类中 java.lang.Object
      • getDecisionStatsDump

        public java.lang.String getDecisionStatsDump()
      • trim

        protected int[] trim​(int[] X,
                             int n)
      • toArray

        protected int[] toArray​(java.util.List<java.lang.Integer> a)
      • getNumberOfHiddenTokens

        public int getNumberOfHiddenTokens​(int i,
                                           int j)
        Get num hidden tokens between i..j inclusive
      • locationDescription

        protected java.lang.String locationDescription()
      • locationDescription

        protected java.lang.String locationDescription​(java.lang.String file,
                                                       java.lang.String rule,
                                                       int line,
                                                       int pos)