Tom Lane <[EMAIL PROTECTED]> writes: > Actually, having traced through it, the problem is obvious: yylex() is > called more than four times and starts to return machine-dependent > garbage after the fourth call.
OK, but why is yylex being calling more than four times? It's called only four times on my host. So there is some _other_ bug that the yylex issue is a symptom of. The problem is, how do we isolate that bug? One way to do it is to use GDB to trace through the same test on both a working host (e.g., Debian stable) and your non-working one, and see where the two behaviors start to diverge.
