On Wed, Feb 12, 2014 at 3:07 AM, Nikodemus Siivola <nikodemus@random-state.net> wrote:
Huh. That's quite a bit more puzzling, but compilation policies may still explain this.

Yes, that turns out to be correct.

After way too many combinations, it appears that the bug is triggered by the combination of

  (safety 0) (space 0) (speed 2+)

It seems to require all three, so maybe that is specific enough to make it easy to inspect for a cause.

-- Scott