[antlr-interest] How to interpret the trace file?

[mzukowski at yci.com]

Mostly you get rule entry and exit plus you can see the lookahead at the
time of each match.  You still need to look at the generated code to figure
out what is going on.  The gcc translator project has some nice traceIn and
traceOut methods which will indent properly and print token names instead of
numbers.  http://www.codetransform.com/gcc.html

Monty

-----Original Message-----
From: micheal_jor <open.zone at virgin.net> [mailto:open.zone at virgin.net]
Sent: Wednesday, January 08, 2003 1:04 AM
To: antlr-interest at yahoogroups.com
Subject: [antlr-interest] How to interpret the trace file?


Hi All,

Is there any documentation that details how to use the trace [and/or 
diagnostic] output file to diagnose recognition problems?.

Does it give any more information than a persistent call stack trace?

Micheal



 

Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/ 


 

Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/