In case anyone's wondering, the undefined behaviour turned out to be caused by using memcpy on overlapping regions. I found this after sleeping :).
-
-
Show this threadThanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
If it’s a timing related thing that’s stack tracing. If it’s stochastic parameters, grab a six pack.
-
It's not timing, but that's about the only thing I can say with confidence. And I might be wrong about that. Isn't C fun...
- 7 more replies
New conversation -
-
-
sounds like luajit
-
Just more evidence that somebody other than me should write runtime systems :)
- 3 more replies
New conversation -
-
-
Quoth the programmer: “I’ll just try this quick fix, won’t take me long”
-
I learned not to say that some time ago :)
End of conversation
New conversation -
-
-
So that "unrelated function" is apparently not so unrelated after all?
-
The evidence suggests that it's important, certainly. But it's not a specific unrelated function. Lots of things have the same effect. For example: map f (map g xs) -- crashes map (f . g) xs -- doesn't crash I guess this is the runtime trying to teach me good style :)
End of conversation
New conversation -
-
-
This Tweet is unavailable.
-
I slept, then fixed it :).
End of conversation
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.