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

Bug 322311

Summary: for CSourceNotFoundDescriptionFactory, enchance getDescription() to ignore address when description is for editor
Product: [Tools] CDT Reporter: Kirk Beitz <kirk.beitz>
Component: cdt-debugAssignee: Ken Ryall <ken.ryall>
Status: CLOSED DUPLICATE QA Contact: Ken Ryall <ken.ryall>
Severity: normal    
Priority: P3 CC: dalexiev, pawel.1.piech
Version: 7.0   
Target Milestone: 7.0.1   
Hardware: All   
OS: All   
Whiteboard:
Attachments:
Description Flags
patch containing code to allow getDescription() to use different formats when being retrieved as an editor name none

Description Kirk Beitz CLA 2010-08-11 01:04:56 EDT
Created attachment 176295 [details]
patch containing code to allow getDescription() to use different formats when being retrieved as an editor name

context: at times, multiple "CSourceNotFound" editors will be opened when viewing frames in the Debug "stack" and then leaving them open during further execution and later viewing, or even at times when disassembly-stepping such contexts.

the problem is exacerbated when the StackFrameDMC objects held by various VM objects have the instruction pointer address associated with them updated; this seems especially prevalent with recent EDC changes to prevent the instruction pointer address from getting stale so that nested variable scoping and variable change highlighting perform correctly, but can be reproduced with DSF-GDB as well.

the attached patch EditorNameForFrameWithoutFilename.patch contains changes for org.eclipse.cdt.debug.core, org.eclipse.cdt.debug.ui and org.eclipse.cdt.dsf.ui that together help create a description name for a frame VM that can be used by the editor so that the name remains the same for the editor even when the address changes.  this allows later editor comparisons to re-find such "CSourceNotFound" editors and re-use them, rather than opening new ones.
Comment 1 Ken Ryall CLA 2010-09-17 17:32:20 EDT

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