[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [platform-debug-dev] Memory view reads before base address
|
Stefan,
This is a good idea, and I'd like to add a couple of additional requests:
- You should be able to specify the base/size or start/end address of a memory
block, so you can safely scroll within that region.
- This should become an attribute of an IMemoryBlockExtension. i.e. (optionally)
ensure the base address and size of a memory block are respected (and thus
automatically set the rendering preferences)
Stefan Bylund wrote:
Hi,
The Memory view reads a bunch of bytes before the specified base
address. This is bad for some kind of embedded systems and core dumps
where you have many small non-consecutive memory snapshots.
The only way to make the Memory view work on such systems is to choose
"Table Rendering Preferences..." in the Memory view's menu and deselect
"Automatically load next page of memory when scrolled to end of buffer".
After that the Memory view respects the base address and does not try to
read a bunch of bytes before it. However, in this mode, you can not
scroll down and automatically fetch more memory, which still can be useful.
Would it be possible if the Memory view was changed so that it always
respects the base address? This would make it much more useful.
Should I file a bug report on this?
Regards,
Stefan
--
Derek