Help with investigating address
Posted: Wed May 27, 2020 6:43 pm
So, say I found an address relevant to what I want to modify.
How can I follow that addresses calls/jumps/etc.?
Or is there a way to see every other address relevant/referencing that address?
Is my assumption correct that I can simply use "step" in debug?
If that is correct, how do I go about timing it?
I find myself confused when trying to use "step", as Im unaware if what its reading back to me is relevant exactly to what Im trying to investigate?
Its also a bit awkward, for instance, what If I want to make an alteration in game and follow that alteration?
but I keep having to switch between mame window/debug window? While "stepping" its halted on an instruction, if I want to make a change in game, I have to hit f5, scramble to grab mouse, click over to mame, then click back to debug window and hit f11.
Im even a bit confused by the step terminology, like "step into" or "step over". Its unclear to me when I want to use what by their title.
If someone could clarify it would be super helpful for me.
So in that instance am I missing the window of opportunity to even view the instructions relevant?
Or is it just a matter of starting the step in the right place first try?
Also, how can I know how far to "step"?
Or is my assumption correct that I would "step" until the change has happened in game?
Another question...
If I found an instruction I wanted to look at in memory, how could I go about finding that address in memory, or disassembly?
I tried doing "find" command, but I couldnt get it to search for more than 1 byte of hex separately, so the results were muddled by single byte results all over the place, rather than the exact whole search. I tried typing it like "find 00000,fffff,FC,FF,FF,FF" and "find 00000,fffff,"FC FF FF FF" and without spaces in quotation. the only search that went through was with comma between each byte.
Thanks in advance, any wisdom or advice is very much appreciated. Im trying to learn, so any help will be great.
Much Love
How can I follow that addresses calls/jumps/etc.?
Or is there a way to see every other address relevant/referencing that address?
Is my assumption correct that I can simply use "step" in debug?
If that is correct, how do I go about timing it?
I find myself confused when trying to use "step", as Im unaware if what its reading back to me is relevant exactly to what Im trying to investigate?
Its also a bit awkward, for instance, what If I want to make an alteration in game and follow that alteration?
but I keep having to switch between mame window/debug window? While "stepping" its halted on an instruction, if I want to make a change in game, I have to hit f5, scramble to grab mouse, click over to mame, then click back to debug window and hit f11.
Im even a bit confused by the step terminology, like "step into" or "step over". Its unclear to me when I want to use what by their title.
If someone could clarify it would be super helpful for me.
So in that instance am I missing the window of opportunity to even view the instructions relevant?
Or is it just a matter of starting the step in the right place first try?
Also, how can I know how far to "step"?
Or is my assumption correct that I would "step" until the change has happened in game?
Another question...
If I found an instruction I wanted to look at in memory, how could I go about finding that address in memory, or disassembly?
I tried doing "find" command, but I couldnt get it to search for more than 1 byte of hex separately, so the results were muddled by single byte results all over the place, rather than the exact whole search. I tried typing it like "find 00000,fffff,FC,FF,FF,FF" and "find 00000,fffff,"FC FF FF FF" and without spaces in quotation. the only search that went through was with comma between each byte.
Thanks in advance, any wisdom or advice is very much appreciated. Im trying to learn, so any help will be great.
Much Love