Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 338858

Summary:	[Pin&Clone] Pin states should be persisted in the launch configuration
Product:	[Tools] CDT	Reporter:	Norman Yee <normankyee>
Component:	cdt-debug	Assignee:	cdt-debug-inbox <cdt-debug-inbox>
Status:	NEW ---	QA Contact:	Jonah Graham <jonah>
Severity:	enhancement
Priority:	P3	CC:	cdtdoug, jonah, pawel.1.piech, zf.fan
Version:	7.0
Target Milestone:	---
Hardware:	PC
OS:	All
Whiteboard:

Description Norman Yee

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.