Date: Tue, 6 Jun 2000 07:07:22 -0700 (PDT) From: gryphon@intech.net To: freebsd-gnats-submit@FreeBSD.org Subject: bin/19056: yacc in 3.4 and 4.0 reports "maximum table size exceeded" Message-ID: <20000606140722.6E22837B8EE@hub.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 19056
>Category: bin
>Synopsis: yacc in 3.4 and 4.0 reports "maximum table size exceeded"
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: freebsd-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Tue Jun 06 07:10:00 PDT 2000
>Closed-Date:
>Last-Modified:
>Originator: Coranth Gryphon
>Release: 3.4R and 4.0R
>Organization:
>Environment:
FreeBSD 3.4-RELEASE #0: Fri May 12 21:44:13 GMT 2000 (GENERIC) i386
FreeBSD 4.0-RELEASE #1: Mon May 8 14:58:16 PDT 2000 (INTECH) i386
>Description:
When using yacc on either platform, a specific grammer results in
the fatal error "maximum table size exceeded". However, according
ORA's book on Yacc, this usually indicates a bug in the yacc program.
In this case, the grammer only has:
340 terminals, 200 nonterminals
615 grammar rules, 920 states
Which is actually significantly less non-terminals, rules and states
than it had when the problem first showed up. I am using bison (1.28)
as countercheck and it works fine.
>How-To-Repeat:
Anything the yacc program is run with the current language grammar.
Unfortunately, I wasn't able to isolate the grammar change that caused
the initial overflow, and developement has had to proceed since then.
If absolutely necessary, I can make the grammar that causes the problem
available under an NDA for testing purposes.
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000606140722.6E22837B8EE>