frigg: slab_pool corruption

[Andy-Python-Programmer]

mlibc panicked at Assertion '!"slab_pool corruption. Possible write to unallocated object"' failed!.

If a rear guard is placed (i.e all malloc calls allocate size + 16) it works. So its most likely an out of bounds access.

[64]

This issue is too generic: there may be multiple different OOB writes happening inside different parts of mlibc and triggered under different circumstances. Can you mention how you triggered the issue?

[ArsenArsen]

it's also extremely unlikely to be in mlibc (or rather, in mlibc in isolation; what program did this? what's the backtrace? etc)