That was admittedly the other pattern, but something is clearly wrong with the sporadic "Result: 0" answer. That particular box won't run --valgrind ("vex amd64->IR: unhandled instruction bytes: 0x66 0xF 0x1F 0x44") so I haven't been able to dig deeper.