Detect memory leaks in tests

[mrgriffin]

Can use KNOWN_LEAKING; to specify that a test is known to leak memory. This is not particularly useful for battle tests, but could be useful for the generic tests introduced by #2696.

The location information is available in regular game builds. Thus it is available for use in debugging leaks in-game too. In the future we should consider replacing it with NULL if NDEBUG is defined. This is not currently possible because the tests do not force NDEBUG to be undefined.

To avoid changing the size of struct MemBlocks, I have stuffed the pointer into unused bits.

Example:

--- a/test/move_effect_absorb.c
+++ b/test/move_effect_absorb.c
@@ -12,6 +12,7 @@ SINGLE_BATTLE_TEST("Absorb recovers 50% of the damage dealt")
+        void *x = Alloc(0x8);

$ make check
Absorb recovers 50% of the damage dealt: FAIL
test/move_effect_absorb.c:15: 8 bytes not freed

[mrgriffin]

Perhaps the semantics should be more like KNOWN_FAILING;, specifically, if you specify KNOWN_LEAKING; maybe it should fail if the test does not leak? At the moment it just suppresses the leak check, i.e. without this set your test will fail if it leaks, but that's it.

If so, how should it interact with KNOWN_FAILING;? Probably not at all? i.e. a KNOWN_FAILING; test should red-FAIL if it leaks and there's not also a KNOWN_LEAKING;?

[AsparagusEduardo]

Please solve conflicts :)

[mrgriffin]

Please solve conflicts :)

Done :)