The memory window won't parse an address that doesn't begin with 0x. Since
Visual Studio strips off the 0x after the first time the address is parsed,
this makes the window hard to use.
It appears that memory address parsing goes through the same path as watch
window variable name parsing. There must be some way to disambiguate addresses
(as opposed to, say, a variabled named "fee" or some such) but we don't know
what it is yet.
Original issue reported on code.google.com by ile...@google.com on 12 Jul 2010 at 3:33
Original issue reported on code.google.com by
ile...@google.com
on 12 Jul 2010 at 3:33