- Using WabbitEmu to check if RAM in a range has been edited
- 28 Dec 2021 05:38:45 am Permalink
I'm using "B_CALL _InsertMem" to give myself 12,000 of free ram starting at $9D95, but apparently I've got some bugs where I'm writing to address beyond that range. I know what the problem is, but I don't know where the problem is. (I'm using a routine to copy tiles from a master set to RAM, but it looks like I've got a few tile tables with invalid data in them, causing the tile copy routine to copy them past my allocated 12,000 data.) Is there a way to ask WabbitEmu to "break" upon a write to a RAM location within a range (from $C000-$E000 for example) rather than manually setting a watchpoint for every, single RAM address in that range?