for Edizon, I usually write down each different memory dump # and the address on paperThat is true. It shows the segment type. Alias is another abstraction above segment type.
I will consider your request. For now move left will jump back one level and you will see the pointer as A+ if the display mode is smart (default)
Post automatically merged:
@dsrules what your opinion on this.
Here is the general scheme of application pointer search.
You need at least two game session to perform a search. You use bookmark to create dump and also record the target address. When you have two or more dump of the same target you can run Breeze in application mode and pick two dump from a list of dumps you have and proceed to perform pointer search. The results will be added to current bookmark file.
The thing is dumps can be used for multiple targets one at a time. As long as a bookmark has the correct static address you can assigned it for pointer search. The problem is helping users to identify which is the matching bookmark. A bookmark file has the meta of the session recorded when created and that get refreshed when a clean up is performed. If a clean up is performed bookmark recorded from a different session will no longer have the static address as per captured but will get a refreshed static address (i.e may be wrong one).
Here is the question:
Is it better to say user you make sure the bookmark file has only bookmark of the correct session and breeze reject if meta of dump and bookmark file don’t match. Or user use name of bookmark to manually keep track
Application pointer search is going to be bound by memory the number of dump that can be used otherwise it is storage and time bound when it comes to num offset, range and depth. May take a long time but I assume most users that perform pointer search are very patient people
I planned to make it support suspend but it’s going all the way until limit then iterate the next one so go for long search likely won’t give good result in short time.
You can run game to test result and do more search if needed. Dump is frozen in time like the PC base pointer search.
Just like Breeze pointer search I am doing it slow and easy. Thinking about it more than coding anything most of the time
for Breeze, if user could edit the pointer search address before a search, I guess the best method, if not using paper, is via BM labeling
for example, if the 1st memory dump for hp is labeled hp1 and the memory dump name is hp1_xxxxxxx
user could label the item address bookmark item1_10DigitsAddress (knowing this address belongs to the hp1... memory dump, the bookmark and label should stay intact after a reboot even when it is in alias


















