Community
Participate
Working Groups
Build Identifier: 201005241228 The C/C++ breakpoint type (label) does not show the proper text. Reproducible: Always Steps to Reproduce: 1. open the disassembly view 2. click on 'Run | Breakpoint Types'
Created attachment 170856 [details] Corrected the bundle name
I got this one.
(In reply to comment #2) > I got this one. I updated the title, I didn't realize the text was from the last bug that I filed.
I was just looking at why we have two *near* identical implementations of IToggleBreakpointsTargetFactory. One in cdt.debug, on in dsf: org.eclipse.cdt.debug.internal.ui.actions.ToggleCBreakpointsTargetFactory org.eclipse.cdt.dsf.debug.internal.ui.ToggleBreakpointsTargetFactory Was going to see if there was some way to consolidate these two, but I'll let you take it from here.
Committed the fix to HEAD. Thanks Patrick. I'll answer John separately.
Comment on attachment 170856 [details] Corrected the bundle name I think this means that we need to update the IP log for the Helios release.
(In reply to comment #4) > I was just looking at why we have two *near* identical implementations of > IToggleBreakpointsTargetFactory. One in cdt.debug, on in dsf: > > org.eclipse.cdt.debug.internal.ui.actions.ToggleCBreakpointsTargetFactory > org.eclipse.cdt.dsf.debug.internal.ui.ToggleBreakpointsTargetFactory > > Was going to see if there was some way to consolidate these two, but I'll let > you take it from here. The first is the original one and works for the CEditor. The second was added for the DSF Disassembly view. This new one could not be added to cdt.debug because it needs access to IDisassemblyPart which is part of the DSF plugins. After the refactoring of the DSF Disassembly view that you did, maybe there is a better way?
(In reply to comment #6) > (From update of attachment 170856 [details]) > I think this means that we need to update the IP log for the Helios release. Woops. I'll email Doug.
(In reply to comment #7) > The first is the original one and works for the CEditor. > The second was added for the DSF Disassembly view. This new one could not be > added to cdt.debug because it needs access to IDisassemblyPart which is part of > the DSF plugins. > > After the refactoring of the DSF Disassembly view that you did, maybe there is > a better way? Well, it seems we could have the DSF one simply extend the cdt.debug one. This would allow it to reuse at least some of the implementation * getToggleTargetDescription(String) * getToggleTargetName(String) * getDebugContext(IWorkbenchPart) * TOGGLE_C_BREAKPOINT_TARGET_ID No need to have the name and description stored in two places. This bug would not have happened had that been the case. Also, note the big old comment at the DSF version that would become mostly irrelevant. Not a big deal though.
*** cdt cvs genie on behalf of mkhouzam *** Bug 315446: Wrong bundle name makes NLS strings fail to be found. [*] Messages.java 1.2 http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.cdt/dsf/org.eclipse.cdt.dsf.ui/src/org/eclipse/cdt/dsf/debug/internal/ui/Messages.java?root=Tools_Project&r1=1.1&r2=1.2
(In reply to comment #9) > Well, it seems we could have the DSF one simply extend the cdt.debug one. This > would allow it to reuse at least some of the implementation > > * getToggleTargetDescription(String) > * getToggleTargetName(String) > * getDebugContext(IWorkbenchPart) > * TOGGLE_C_BREAKPOINT_TARGET_ID > > No need to have the name and description stored in two places. This bug would > not have happened had that been the case. Also, note the big old comment at the > DSF version that would become mostly irrelevant. > > Not a big deal though. Hadn't thought of it. We can do it when the plugin goes to 3.0...
