Is it possible to catch overwriting of libumem's redzone? I uses libumem to analyze a memory corruption and found that redzone of some block is the following:
...
feedface edfecefa
8014822 18a0a5ea
...
and all blocks after this are swapped the same way. Need to find out where/how it could occur.