Bug 4614

Summary:	Memory Window: There is no way to select what address range/space is being examined
Product:	frysk	Reporter:	Kris Van Hees <kris.van.hees>
Component:	general	Assignee:	Kris Van Hees <kris.van.hees>
Status:	RESOLVED FIXED
Severity:	normal
Priority:	P2
Version:	unspecified
Target Milestone:	---
Host:		Target:
Build:		Last reconfirmed:
Project(s) to access:		ssh public key:
Bug Depends on:
Bug Blocks:	3119, 3200

Description Kris Van Hees 2007-06-11 18:26:09 UTC

The application can have multiple disjoint address ranges that might be
interesting to exam.  The default range being shown is the executable code from
the current program counter, which is often within the least interesting memory
range because it is 1) already available in the disassembly window, 2) usually
doesn't actually change.

The memory window does not provide any functionality to select a different
address range other than 'scrolling' through the address range provided by the
spin buttons, which is both impractical and will often lead to invalid memory
accesses.

Comment 1 Andrew Cagney 2007-06-20 17:41:24 UTC

There can be a lot of segments to choose from, firefox has 320.
The user could select the segment, and then specify the offset.
Would replace the "pc" information in the memory window case.

Comment 2 Kris Van Hees 2007-06-20 18:42:16 UTC

Actually, what I suggested was making it possible for the user to select the
segment to work in, and that within the segment the user could then still either
use arbitrary addresses or specify an offset from the base address.  It offers
an additional mode of specifying a valid address.

This can be expanded by adding in a default segment that covers the entire
address range (allowing any address to be specified).  In that case, an offset
is identical to an actual address.

Comment 3 Zhao Shujing 2007-09-30 01:40:29 UTC

2007-09-30  Zhao Shujing <pearly.zhao@oracle.com>

        * gladedir/memorywindow.glade: Change the top text "current program
        counter" to segment combox. Fixes #4614 and #4619.
        * gladedir/disassemblywindow.glade: Ditto.
        * memory/MemoryWindow.java: Added handling for segment.
        Added warning dialogs when the address can't be accessed and when the
        symbol is not in current context.
        Added handling when too many rows be added. Fixes #4870.
        * disassembler/DisassemblyWindow.java: Ditto.

Comment 4 Zhao Shujing 2007-09-30 01:41:28 UTC

*** Bug 4619 has been marked as a duplicate of this bug. ***