Re: memory window: bug wrt endianness

[Ruppert <ru at swb dot siemens dot de>]

...
> >
> >I think I found a bug with the implementation of the memory...
> >When I open the memory window, it displays 0x00000001 in the field
> >which corresponds to address 0x8049518. Then I click into this field,
> >change this to 0x00000002 and press Enter. The field continues to
> >display 0x00000002. When I scroll up or down in the memory window
> >the contents of this field suddenly changes to 0x02000000. This value
> >appears also in the console window:
> >
> >(gdb) p /x i
> >$3 = 0x2000000
> 
> Insight 5.1.1:
> 
> I tried this just out of curiosity and found out that I can't edit memory 
> at all. If I change a value in the memory window and click "update now" the 
> previous value reappears. Editing from console window works, though.

You need to press "Enter" after changing the value (at least it works like this
in my case). If I omit this, then, indeed, the edited value gets overwritten
from the target when I click "update now".

> 
> BTW, how can you scroll the memory window? If I set the memory address to 
> some free RAM location, I can only move within the window. Clicking the 
> little arrows in the "address" edit box sometimes moves one line at a time 
> (not back with the opposite pointing arrow) and finally causes jumping into 
> oblivion. Should there be normal PgUp/PgDn/Arrow key functionality?

Poor wording from my part. I meant the arrows in the "Address" edit box. Those
work as expected, in my case: they "move" the memory window in the indicated
direction.


---------------------------
Dieter Ruppert
RTS GmbH
ru@swb.siemens.de