Read the docs on what the -debug option does. It causes the generated code to listen on a TCP port until ANTLRWorks connects to it. Hence it hangs with gunit.
Jim > -----Original Message----- > From: [email protected] [mailto:antlr-interest- > [email protected]] On Behalf Of joestelmach > Sent: Friday, February 12, 2010 7:34 AM > To: [email protected] > Subject: [antlr-interest] running gUnit tests with -debug generated > parser > > > If I generate my parser with the -debug option, gUnit tests will not > run (the > process prints no information, and never returns.) Running gUnit on > the > same parser generated without the -debug option works just fine. > > Any ideas? > -- > View this message in context: http://n2.nabble.com/running-gUnit-tests- > with-debug-generated-parser-tp4561697p4561697.html > Sent from the ANTLR mailing list archive at Nabble.com. > > List: http://www.antlr.org/mailman/listinfo/antlr-interest > Unsubscribe: http://www.antlr.org/mailman/options/antlr-interest/your- > email-address List: http://www.antlr.org/mailman/listinfo/antlr-interest Unsubscribe: http://www.antlr.org/mailman/options/antlr-interest/your-email-address -- You received this message because you are subscribed to the Google Groups "il-antlr-interest" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/il-antlr-interest?hl=en.
