[antlr-interest] Problems debugging large grammar in VisualStudio 2005

[Loring Craymer]

After thinking a little more, I realized that the
"unsigned short" probably has to do with the MS .obj
format; it may not be fixable.  I don't think that the
inability to handle large files is a weakness of the
tools--for most apps, it is a "feature".

--Loring

--- Jim Idle <jimi at temporal-wave.com> wrote:

> As an aside to this, the number of lines will reduce
> before too long,
> though it has no effect on performance. I will be
> folding some of the
> exception handling etc into external functions and
> getting rid of some
> unnecessary whitespace. It might help with some
> tools, though in general
> I have found VS2005 to be exceptionally good.
> 
> Jim
> 
> > -----Original Message-----
> > From: antlr-interest-bounces at antlr.org
> [mailto:antlr-interest-
> > bounces at antlr.org] On Behalf Of Loring Craymer
> > Sent: Friday, July 13, 2007 8:51 AM
> > To: troy runkel; ANTLR mail-list
> > Subject: Re: [antlr-interest] Problems debugging
> large grammar in
> > VisualStudio 2005
> > 
> > Sounds like there is an "unsigned short" index
> > somewhere in the MS code.  If so, you will have to
> get
> > a bug fix to get past 65535 lines (and answer the
> > inevitable "why are you debugging a 100K line
> file?"
> > question).
> > 
> > --Loring
> > 
> > --- troy runkel <trunkel at gmail.com> wrote:
> > 
> > > I'm using ANTLR v3 and the C target.  I have a
> large
> > > grammar file
> > > (2500 lines) which builds into an even larger C
> > > parser file (107000
> > > lines).  When debugging the generated parser in
> > > Visual Studio 2005, if
> > > I attempt to step into a function located in the
> > > bottom half of the
> > > file the debugger won't display the correct
> source
> > > location.  This
> > > behavior is fairly consistent.  I can step
> > > through/into functions in
> > > the top half of the file without problems.  As
> soon
> > > as I step into a
> > > function in the bottom half of the file the
> debugger
> > > displays
> > > incorrect source information.  I can debug at
> the
> > > assembly level, but
> > > that's a bit of a pain.
> > >
> > > I realize this is more of a compiler issue than
> an
> > > ANTLR issue, but
> > > before I attempt to navigate through the
> labyrinth
> > > of Microsoft
> > > technical support I thought I'd check here
> first.
> > > Has anybody seen
> > > this sort of behavior?  Thanks.
> > >
> > > Troy Runkel
> > >
> > 
> > 
> > 
> > 
> >
>
_______________________________________________________________________
> > _____________
> > Boardwalk for $500? In 2007? Ha! Play Monopoly
> Here and Now (it's
> > updated for today's economy) at Yahoo! Games.
> >
>
http://get.games.yahoo.com/proddesc?gamekey=monopolyherenow
> 



      ____________________________________________________________________________________
Park yourself in front of a world of choices in alternative vehicles. Visit the Yahoo! Auto Green Center.
http://autos.yahoo.com/green_center/