[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: MAXTABLE & Serious issues with bison 1.30
From: |
Tim Van Holder |
Subject: |
Re: MAXTABLE & Serious issues with bison 1.30 |
Date: |
03 Jan 2002 14:22:31 +0100 |
On Thu, 2002-01-03 at 13:46, Akim Demaille wrote:
> >>>>> "Tim" == Tim Van Holder <address@hidden> writes:
>
> Tim> Yes, but now try with 'bison -d'; plain bison did work with 1.30
> Tim> as well.
>
> ???
>
> /tmp % ~/src/bison-1.29/tests/bison -d i4gl.y nostromo
> 13:41
> i4gl.y contient 31 useless nonterminals et 52 useless rules
> i4gl.y contient 1059 shift/reduce conflicts and 617 reduce/reduce conflicts.
> i4gl.y:4110: erreur fatale: taille maximale de la table (32767) dépassée
> /tmp % ~/src/bison-exp/tests/bison -d i4gl.y nostromo Err
> 1
> i4gl.y contient 31 useless nonterminals et 52 useless rules
> i4gl.y contient 1059 shift/reduce conflicts and 617 reduce/reduce conflicts.
> i4gl.y:4110: erreur fatale: taille maximale de la table (32767) dépassée
Oh right - my bad. If you don't increase MAXTABLE, the grammar indeed
won't work with the default start symbol (module).
But the segfault also occurs if another start symbol (smaller subset) is
used; try using move_cmd instead of module (currently commented out).
That should allow you to reproduce the crash.