Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 338858 - [Pin&Clone] Pin states should be persisted in the launch configuration
Summary: [Pin&Clone] Pin states should be persisted in the launch configuration
Status: NEW
Alias: None
Product: CDT
Classification: Tools
Component: cdt-debug (show other bugs)
Version: 7.0   Edit
Hardware: PC All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: cdt-debug-inbox@eclipse.org CLA
QA Contact: Jonah Graham CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-03-03 16:30 EST by Norman Yee CLA
Modified: 2021-06-17 11:28 EDT (History)
4 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 Norman Yee CLA 2011-03-03 16:30:30 EST 
Build Identifier: I20110127-2034

If I launch a multi-core session, open a bunch of views like the disassembly view, registers view, etc., pin them to a core, terminate the launch, and shut down Eclipse, the next time I start Eclipse and launch the same session, I'd expect the views to be pinned to the same cores as before.


Reproducible: Always

Steps to Reproduce:
1. launch a multi-core debug configuration
2. open the disassembly view
3. pin the disassembly view to core 0
4. clone the disassembly view
5. pin the cloned disassembly view to core 1
6. exit Eclipse
7. start up Eclipse
8. launch the debug configuration.  The two disassembly views are now unpinned.
 I'd expect them to be pinned to the same cores.