Re: Flex 2.5.35: fatal flex scanner internal error--end of buffer missed

Clint O <clint.olsen@gmail.com>
Sat, 22 Jan 2011 20:12:22 -0800 (PST)

          From comp.compilers
Related articles
Flex 2.5.35: fatal flex scanner internal error--end of buffer missed clint.olsen@gmail.com (Clint O) (2011-01-22)
Re: Flex 2.5.35: fatal flex scanner internal error--end of buffer miss clint.olsen@gmail.com (Clint O) (2011-01-22)
| List of all articles for this month |
From: Clint O <clint.olsen@gmail.com>
Newsgroups: comp.compilers
Date: Sat, 22 Jan 2011 20:12:22 -0800 (PST)
Organization: Compilers Central
References: 11-01-104
Keywords: flex, errors, question
Posted-Date: 23 Jan 2011 21:34:30 EST

On Saturday, January 22, 2011 3:38:13 PM UTC-8, Clint O wrote:
> [I see notes saying that if you longjmp out of the lexer and call it
> again without resetting the input stream, this error often results.
> -John]


Yes, I read something to the effect that once you reach an EOF you
must reset yyin (or something to that effect). This sort of begs the
question of how you'd do error recovery when you get a syntax error on
the last token of the input. Does this seem like the expected
behavior to you? I don't have any more input to give it, so I don't
know what I'm supposed to set yyin to once I've reached EOF.


Thanks,


-Clint
[You can call yyrestart(yyin) but based on offline discussion this sounds
to me like a smashed pointer bug. -John]


Post a followup to this message

Return to the comp.compilers page.
Search the comp.compilers archives again.