[antlr-interest] ANTLR V3, ANTLRWorks and C/C++ Target

Jim Idle jimi at temporal-wave.com
Thu Aug 9 22:34:17 PDT 2007


ANTLRWorks debugging for the C target is not yet implemented. In general
I use Visual Studio or gdb and debug the C directly. It will be
forthcoming, but there are 50 other things to do too :-)

Jim

> -----Original Message-----
> From: antlr-interest-bounces at antlr.org [mailto:antlr-interest-
> bounces at antlr.org] On Behalf Of Johannes Luber
> Sent: Wednesday, August 08, 2007 9:00 AM
> To: antlr-interest at antlr.org
> Subject: Re: [antlr-interest] ANTLR V3, ANTLRWorks and C/C++ Target
> 
> Martin Kortmann wrote:
> > D:\Martins\Entwicklung\test_antlr>java -cp
> > antlr-3.0.jar;antlr-runtime-3.0.jar;stringtemplate-3.0.j
> > ar;antlr-2.7.7.jar org.antlr.Tool -debug -o outdir test.g
> > ANTLR Parser Generator  Version 3.0 (May 17, 2007)  1989-2007
> > error(10):  internal error: group CDbg line 33: template outputFile
> has
> > no region called imports
> >
> > error(10):  internal error: group CDbg line 78: template
> genericParser
> > has no region called superClassName
> >
> > error(10):  internal error: group CDbg line 160: template dfaState
> has
> > no region called noViableAltException
> >
> > error(10):  internal error: group CDbg line 162: template
> dfaStateSwitch
> > has no region called noViableAltException
> >
> > D:\Martins\Entwicklung\test_antlr>
> >
> >
> >
> > Thank you, the same problem
> >
> > Martin
> 
> I just remembered that the newest daily build broke all languages
> (except Java) at least for debugging. I'm not sure when that is fixed
> but for now you can use an older version and hope that you don't
> stumble
> on an already fixed bug.
> 
> Best regards,
> Johannes Luber


More information about the antlr-interest mailing list