search

keefehiggins / bizhawk

Automatically exported from code.google.com/p/bizhawk
0 stars 0 forks source link

Add read/write monitoring to RAMsearch/RAMwatch! #154

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
In the popular memory scanner utility Cheat Engine you can right click an entry 
in your address list and click on "Find out what accesses this address"/"Find 
out what write to this address" to have it track all reads/writes to the 
address.

Something similar to this would be very useful for TASing in bizhawk. For 
example it would allow one to quickly find whole structures of related values 
with some knowledge of assembly. Being able to replace the respective assembly 
code by code that does nothing (also something CE can do) would vastly help 
with reverse-engineering things in a game too.

Original issue reported on code.google.com by james.su...@yahoo.de on 11 Apr 2014 at 3:57

GoogleCodeExporter commented 9 years ago 
(Supposed to be an Enhancement not a Defect, was unable to find a way to change 
that when submitting)

Original comment by james.su...@yahoo.de on 11 Apr 2014 at 3:58

GoogleCodeExporter commented 9 years ago

Original comment by adeli...@tasvideos.org on 11 Apr 2014 at 4:46

GoogleCodeExporter commented 9 years ago 
I assume this would be equally valuable for the Hex Editor

Original comment by adeli...@tasvideos.org on 11 Apr 2014 at 5:22

GoogleCodeExporter commented 9 years ago 
Yeah for anything where you can work with addresses, yes. Of course one could 
just "add to RAM watch" in the Hex Editor...

It is to be noted that such monitoring might get power-consuming if used on too 
many addresses at once, so somehow automatically monitoring addresses the user 
hasn't specifically selected should be avoided (e.g. having this on by default 
for all addresses, similar to the change counter which is always active)

In any case, thanks for noticing this so quickly Adelikat, your activity 
positively surprises me. ;)

Original comment by james.su...@yahoo.de on 11 Apr 2014 at 6:00

GoogleCodeExporter commented 9 years ago

Original comment by zero...@zeromus.org on 9 Jun 2014 at 4:06

GoogleCodeExporter commented 9 years ago

Original comment by zero...@zeromus.org on 10 Jun 2014 at 10:50