When searching for a value in the memory debugger, it works fine using physical addresses, but it will give an "Address out of range" error if searching using virtual addresses. However, I can only view values in memory in the virtual address range.
This means I have to search in physical memory, then manually change the address to it's virtual counterpart, and see if it's what I want. If not, change it back, and search again.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
For example, I start by setting the address to 0. I search something as usual, and say it finds a result at 6BCC. I then have to change the address to 80006BCC, to see if I found what I was looking for. If not, I have to change it back to 6BCC, and search again.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
This is really clunky, and I'm wondering if this is a known bug, or if there is any known fix to this.
This means I have to search in physical memory, then manually change the address to it's virtual counterpart, and see if it's what I want. If not, change it back, and search again.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
For example, I start by setting the address to 0. I search something as usual, and say it finds a result at 6BCC. I then have to change the address to 80006BCC, to see if I found what I was looking for. If not, I have to change it back to 6BCC, and search again.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
This is really clunky, and I'm wondering if this is a known bug, or if there is any known fix to this.