fatal flex scanner internal error--end of buffer missed
relson at osagesoftware.com
Sat Jan 11 00:20:42 EST 2003
At 12:13 AM 1/11/03, you wrote:
>On Fri, Jan 10, 2003 at 11:53:16PM -0500, David Relson wrote:
> > Is the above message familiar? It's at the root of my procmail/bogofilter
> > failure/retry loop.
>Yes. That's what led me to the base64 error.
>The boundary, in this case, begins with '=' chars, which causes
>the base64 decoder to fail, but in the process, it returns a negative
>count, which gets passed to the flex code, which barfs.
> > I've been running a bogofilter snapshot built 01/08 21:30 and have the
> > message that causes the error. With current cvs source, the error doesn't
> > happen.
>Because the new code checks for boundaries and does not attempt to decode
> > Do you think we need to pursue this?
>Yes, since the original problem still exists. The base64 decoder should
>fail gracefully on undecodable input.
You seem to have an approach in mind for handling the problem. I
don't. Would you care to take the lead on this one? Do you want/need
another copy of the message?
More information about the Bogofilter-dev