Bug 299690 - [Memory Browser] support multiple memory pages
Summary: [Memory Browser] support multiple memory pages
Status: NEW
Alias: None
Product: CDT
Classification: Tools
Component: cdt-memory (show other bugs)
Version: 6.0.1   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: cdt-debug-inbox@eclipse.org CLA
QA Contact: Jonah Graham CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-01-14 14:22 EST by Alain Lee CLA
Modified: 2020-09-04 15:24 EDT (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Alain Lee CLA 2010-01-14 14:22:43 EST 
We have devices that have multiple memory pages (e.g. Program, Data, I/O) We have requirements to open Memory View/Memory Browser then display the memory for a specific starting addres for a specific memory page.
Comment 1 John Cortell CLA 2010-01-14 14:58:51 EST 
This capability is already present in the Memory view, for CDI debug sessions. CDI has an API that allows the client to specify what memory spaces are involved in the debug session. CDT automatically puts up a New Memory Monitor dialog that allows the user to choose the memory space.

There's even a global pref to make code and memory spaces available for gdb/mi sessions

   Window > Preferences > C/C++ > Debug > GDB MI > 

There's a checkbox: Support distinct code and data memory spaces

I don't know what the DSF debugger has done in this area.
Comment 2 Alain Lee CLA 2010-01-14 16:24:12 EST 
We are interested in seeing this being supported by Memory Browser and DSF.