Matthew, I think there is a problem with the way the native backend handles MLton_bug. I had a buggy version of MLton that actually generated code that called MLton_bug, and the result produced was not correct. Of course, there's no SML example I can send you, but if you could look into it, that would be great.