It's inside MorphOS - connect terminal to yours Pegasos serial port and you will see enforcer-like debug output, or use ramdebug to get those hits without other computer.
didn't anything change about this? i'm working on my large project, but it from time to time dies... probably because of some illegal hits. any way to catch them and display them simplier than by ramdebug? i have also the ramdebuglog viewer, but it can't compare with enforcer. it is even possible to implement it with morphos?
is there a way to catch ramdebug log completely? and to filter it, to not to display those non important information? here it's limited to (afaik) 256 kb, and it's not enough... when one hit happens, than it's covered by millions of other hits... which removes those first (important) hits...
@Henes: thanks! but this doesn't solve my problem with ramdebug overload. is there a way to expand the ramdebug log size limitation? or to limit the amount of the debugging data?