Bug 223882 - [breakpoints] default breakpoint working set not exported / imported
Summary: [breakpoints] default breakpoint working set not exported / imported
Status: ASSIGNED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 3.4   Edit
Hardware: PC All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-Debug-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: helpwanted
Depends on:
Blocks:
 
Reported: 2008-03-25 12:09 EDT by Michael Rennie CLA
Modified: 2019-09-25 05:20 EDT (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Rennie CLA 2008-03-25 12:09:22 EDT
if you have breakpoints in a default working set and then export them, it appears as though the working set information is not exported (causing the working set to not be recreated on import)

Steps

1. create a breakpoint working set BPWS1 and make it the default
2. create a second breakpoint working set BPWS2
3. add some breakpoints (move some from BPWS1 to BPWS2)
4. export all breakpoints
5. delete all breakpoints and breakpoint working sets
6. import the breakpoints you just exported (check on 'create working sets..')

Happens:

all of the breakpoints are imported and the non-default working set is created (BPWS2), but not BPWS1

Expected:

all breakpoints are imported and all working sets are recreated

Example of one of the exported breakpoints that belonged to BPWS1 (the default working set):

<breakpoint enabled="true" persistant="true" registered="true">
<resource path="/org.eclipse.debug.ui/ui/org/eclipse/debug/internal/ui/launchConfigurations/LaunchConfigurationsDialog.java" type="1"/>
<marker charStart="4353" lineNumber="-1" type="org.eclipse.jdt.debug.javaWatchpointMarker">
<attrib name="org.eclipse.jdt.debug.core.modification" value="true"/>
<attrib name="charEnd" value="4396"/>
<attrib name="org.eclipse.debug.core.enabled" value="true"/>
<attrib name="org.eclipse.debug.core.id" value="org.eclipse.jdt.debug"/>
<attrib name="message" value="Watchpoint:LaunchConfigurationsDialog [access and modification] - fgCurrentlyVisibleLaunchConfigurationDialog"/>
<attrib name="org.eclipse.jdt.debug.core.suspendPolicy" value="2"/>
<attrib name="org.eclipse.jdt.debug.ui.JAVA_ELEMENT_HANDLE_ID" value="=org.eclipse.debug.ui/ui&lt;org.eclipse.debug.internal.ui.launchConfigurations{LaunchConfigurationsDialog.java[LaunchConfigurationsDialog^fgCurrentlyVisibleLaunchConfigurationDialog"/>
<attrib name="org.eclipse.jdt.debug.core.typeName" value="org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationsDialog"/>
<attrib name="charStart" value="4353"/>
<attrib name="org.eclipse.jdt.debug.core.access" value="true"/>
<attrib name="org.eclipse.jdt.debug.core.auto_disabled" value="false"/>
<attrib name="org.eclipse.jdt.debug.core.fieldName" value="fgCurrentlyVisibleLaunchConfigurationDialog"/>
</marker>
</breakpoint>

The above definition is missing the workingset_id and workingset_name attributes
Comment 1 Eclipse Genie CLA 2019-09-23 09:44:08 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.
Comment 2 Sarika Sinha CLA 2019-09-25 05:20:08 EDT
Still the same.