Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 355431 - [Memory Browser] Memory Space and Go To Address do not reflect the correct settings when the rendering is opened throught another plugin
Summary: [Memory Browser] Memory Space and Go To Address do not reflect the correct se...
Status: CLOSED DUPLICATE of bug 339708
Alias: None
Product: CDT
Classification: Tools
Component: cdt-memory (show other bugs)
Version: 8.0   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: cdt-debug-inbox@eclipse.org CLA
QA Contact: Ted Williams CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-08-22 15:53 EDT by Alain Lee CLA
Modified: 2011-09-21 14:37 EDT (History)
1 user (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 2011-08-22 15:53:10 EDT 
MemoryBrowser provides an API performGo(boolean inNewTab, final String expression, final String memorySpaceId) to allow other plugins to open the Memory Browser and to display the memory data for a specific memory space and an address. When this API is called from other plugins, the rendering is created and displays the correct data. However, the Memory Space box and the Go To Address are not updated to reflect the parameters specified in the performGo() API.
Comment 1 Alain Lee CLA 2011-09-21 14:37:44 EDT 

*** This bug has been marked as a duplicate of bug 339708 ***