I have a branch where, if I add one more #[test] to core then valgrind will abort with an internal assertion failure. I don't have the message here but the valgrind source indicates its a sanity check about function size. Presumably our test harness is generating a main function that is larger than anything valgrind expects to see in the real world.