|Delta lost when breakpoint change merged with breakpoint add? [message #479873]
||Wed, 12 August 2009 16:22
| Joe Luebker
Registered: July 2009
I ran across an issue that is related to how the eclipse breakpoint
manager handles breakpoint changes while handling breakpoint adds. It
appears that the code that I will reference came in from a bug for
What I am seeing in the commercial debugger that I work on is that
sometimes a change notification can be sent but the delta for the change
appears to have been lost or at least a breakpoint changes handler can't
recognize any change in the provided delta. This open happens in a test
environment where I can quickly create a breakpoint and change is
(setting the enabled attribute in my case).
Without a reliable way to reproduce it I wanted to try to describe what
I am seeing and find out if anyone else has reported such an issue or
believes this to be a problem with the Eclipse breakpoint manager.
1. Quickly create a breakpoint and modify it.
2. In BreakpointManager.PostChangeVistor.visit() the marker for the
given delta is added to the fPostChangMarkderChanged set. Notice that
only the marker is added and the delta is not.
3. In BreakpointManager.BreakpointManagerVistor.handleAddBreakpoin t()
the marker is noticed in the fPostChangMarkersChanged set and
handleChangeBreakpoint() is called passing the delta that was passsed
4. In my debugger's handler for the breakpoint changed event nothing
appears to be different between the marker on the breakpoint and the
given marker delta. Note that the kind on the delta is actually a
IResourceDelta.ADDED and not a CHANGED. Not being able to see any
difference in the breakpoint marker vs. the delta results not being able
to update my debugger engine with the breakpoint change.
I guess an option here would be to reinstall the breakpoint when my
breakpoint change handler received a delta with the kind of ADDED but
that is not the preferred solution.
Powered by FUDForum
. Page generated in 0.01759 seconds