I assume, that this bug does not exist in the current ttthreeparser package, which is in unstable since 2005-01-04. Unfortunately, it depends on a newer ANTLR version, but the state of ANTLR is unclear to me. Could the ANTLR maintainers please comment? Thanks. Cheers, W. Borgert RM: If this problem cannot be solved easily, I recommend to remove ttthreeparser from testing. The package is not in woody anyway.