Re: any lex/yacc debuggers????

"Scott Nicol" <sbnicol@mindspring.com>
10 Apr 2002 00:16:14 -0400

          From comp.compilers

Related articles
any lex/yacc debuggers???? varunyagain@rediffmail.com (2002-04-06)
Re: any lex/yacc debuggers???? sbnicol@mindspring.com (Scott Nicol) (2002-04-07)
Re: any lex/yacc debuggers???? k.prasad@attbi.com (Kamal R. Prasad) (2002-04-07)
Re: any lex/yacc debuggers???? sbnicol@mindspring.com (Scott Nicol) (2002-04-10)
Re: any lex/yacc debuggers???? sbnicol@mindspring.com (Scott Nicol) (2002-04-13)
Re: any lex/yacc debuggers???? lex@cc.gatech.edu (Lex Spoon) (2002-04-29)
| List of all articles for this month |

From: "Scott Nicol" <sbnicol@mindspring.com>
Newsgroups: comp.compilers
Date: 10 Apr 2002 00:16:14 -0400
Organization: EarthLink Inc. -- http://www.EarthLink.net
References: 02-04-034 02-04-047 02-04-057
Keywords: yacc, debug
Posted-Date: 10 Apr 2002 00:16:14 EDT

"Kamal R. Prasad" <k.prasad@attbi.com> wrote in message
> Bison has a debug option to tell you which production is being reduced (so
> you can actually see handle pruning etc).


It tells you reductions, but not states. y.output (produced using the
-v option) will give you all the states and shifts. Recode bison to
generate the same info that goes into y.output in to a usable table
and add some hooks so yyparse can make a call at every state change,
then you have the basis for a Yacc debugger.
--
Scott Nicol
sbnicol@mindspring.com
[If you turn on YYDEBUG in Berkeley yacc, you get a blow by blow report
on what tokens it reads, what state it shifts into, and what rules it
reduces. The info is all there if you wanted tart it up into a video
debugger. -John]



Post a followup to this message

Return to the comp.compilers page.
Search the comp.compilers archives again.