[antlr-interest] Problems debugging large grammar in VisualStudio 2005
Jim Idle
jimi at temporal-wave.com
Mon Aug 27 15:11:58 PDT 2007
> -----Original Message-----
> From: antlr-interest-bounces at antlr.org [mailto:antlr-interest-
> bounces at antlr.org] On Behalf Of troy runkel
> Sent: Monday, August 27, 2007 1:49 PM
> To: antlr-interest at antlr.org
> Subject: Re: [antlr-interest] Problems debugging large grammar in
> VisualStudio 2005
>
> I wanted to follow up on this issue and report what I've learned in
> case anybody else runs across this problem. I contacted Microsoft
> Support and opened a case regarding this issue. It turns out that the
> Visual Studio 2005 debugger uses an unsigned short to track line
> number information. This means that the debugger will only work on
> source files up to 64k lines long. The next release of Visual Studio
> is code named Orcas; the one after that Orcas+1. Microsoft is not
> planning to fix this limitation until Orcas+1, which could be several
> years.
>
> Microsoft Support suggested a couple of workarounds for this issue.
>
> 1) Use WinDbg instead of the Visual Studio debugger. Apparently the
> code in WinDbg is more recent and uses 32-bit variables to track line
> number information.
>
> 2) Break up the ANTLR generated lexer and parser files into multiple
> source files each less than 64k lines long.
>
> Does ANTLR already have a good method of breaking up the generated
> files?
No ;-).
However I am going to work on reducing the number of lines I guess ;-) Also the next release may reduce the number of lines too.
Jim
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.5.484 / Virus Database: 269.12.9/975 - Release Date: 8/26/2007 9:34 PM
More information about the antlr-interest
mailing list