YACC-LEX parsing overflow

[Chuck Dillon]

Alvaro Puente wrote:

> Actually, I'm using bison-flex, and I'm afraid the options you mention
> does not appear in manpage.
>
> Regarding the error I get, using purify it shows SOF: Stack overflow
> in function yyparse(), before the process dies (core dump).
> More precisely, the error is found in "bison.simple" file, when calling
> "alloc" function.

What does it say if you enter 'limit' at your commandline? Perhaps
your stacksize limit is set too low and the bison code isn't doing
enough error checking to handle it elegantly.

-- ced




--
Chuck Dillon
Senior Software Engineer
NimbleGen Systems Inc.

[Martin Jost]

"Alvaro Puente" <alvaro.puente-gonzalez@ece.ericsson.se> schrieb im Newsbeitrag news:bek1ft$dfc$1@newstree.wise.edt.ericsson.se...

> "Chuck Dillon" <cdillon@nimblegen.com> wrote in message
> news:3F0D7FDB.1080807@nimblegen.com...

> > What is the exact error message you are getting? Are you exceeding one
> > of the configurable lex table sizes? See the lex manpage about %p, %n,
> > %o and the like.

> Actually, I'm using bison-flex, and I'm afraid the options you mention
> does not appear in manpage.
>
> Regarding the error I get, using purify it shows SOF: Stack overflow
> in function yyparse(), before the process dies (core dump).
> More precisely, the error is found in "bison.simple" file, when calling
> "alloc" function.

Maybe your grammar runs in some sort of (near) endless-recursion.
Try to track down, what bison is doing at that time.
See "Tracing Your Parser" in the info-file for bison.

HTH

Martin

[Alvaro Puente]

"Chuck Dillon" <cdillon@nimblegen.com> wrote in message
news:3F0DD192.3030504@nimblegen.com...

> Alvaro Puente wrote:

> > Actually, I'm using bison-flex, and I'm afraid the options you mention
> > does not appear in manpage.
> >
> > Regarding the error I get, using purify it shows SOF: Stack overflow
> > in function yyparse(), before the process dies (core dump).
> > More precisely, the error is found in "bison.simple" file, when calling
> > "alloc" function.

>
> What does it say if you enter 'limit' at your commandline? Perhaps
> your stacksize limit is set too low and the bison code isn't doing
> enough error checking to handle it elegantly.
>

limit showed a stacksize of 8192 kbytes. I increased it to 81920 kbytes
(%> limit stacksize 81920 kbytes)
and now it works! THANKS!!

Do you know how can I increase stack size from C code? I can use
a "system" call, but I would prefer it to do it using some function.

/Alvaro