I have never used dynload but I dont think C++ would be anymore unsafe than C code.It is language agnostic. I hope other MorphOS developer familiar with dynload can shed some light...

By switching to use memory list based memory system (this is option in boot image command line) you could maybe get grip of it. With memory lists corruption is reported rapidly (often small free block follow allocated memory chunk and corruption is detected quickly). With TLSF corruption is more hideous. Wipeout should catch it, though. IIRC there is an option to check pre- and postwall at anytime. By sending a signal (CTRL-E?) or start Wipeout another time... I cant remember right now. (I am travelling ATM.)

[ Edited by itix 12.06.2014 - 19:58 ]