Closed GoogleCodeExporter closed 9 years ago
I think RAM search was fixed/corrected in 1.9.0. Please test it. If it is
still causing problems, let me know.
Original comment by hegyak
on 22 Nov 2014 at 1:57
The real issue is that Ram Watch and Ram Search were showing the original value
rather than the frozen value (the value was in fact frozen, if viewed in the
Hex Editor it would show it working as intended)
Fixed in revision 8269
Original comment by adeli...@tasvideos.org
on 29 Nov 2014 at 12:46
Original issue reported on code.google.com by
Gerard.C...@gmail.com
on 21 Nov 2014 at 9:06