Community
Participate
Working Groups
The breakpoints view in CDT, unlike most of the other views, does not support refreshing. The bug is to add refreshing support. Although GDB appears to normally provide all the necessary async messages (e.g breakpoint-created), under some GDB-like debuggers it is desirable to be able to force a refresh.
New Gerrit change created: https://git.eclipse.org/r/118716
New Gerrit change created: https://git.eclipse.org/r/118715
New Gerrit change created: https://git.eclipse.org/r/118714
Gerrit change https://git.eclipse.org/r/118714 was merged to [master]. Commit: http://git.eclipse.org/c/cdt/org.eclipse.cdt.git/commit/?id=377374febb42e707cf84597eb5caf3e49ad1dfe4
Gerrit change https://git.eclipse.org/r/118715 was merged to [master]. Commit: http://git.eclipse.org/c/cdt/org.eclipse.cdt.git/commit/?id=8934f52ae631c7f7bb2681d67361f6b5cfbcc1c1
Hi Jonah, I am working on 532076. I am trying to understand how the refresh and synchronize logic works? How the user can invoke it?
Great, I am glad to hear that you are looking at Bug 532076 - it is something that never got revisited by me :-( The refresh buttons need to be enabled by the user. Window -> Perspective -> Customize Perspective -> Action Set Availability (tab) -> Debug Update Modes (checkbox) See https://imgur.com/XqDZ7RG.png That makes the Refresh button visible in all applicable views of CDT (including the Breakpoints view) You can also enable it in a product by adding to some plugin.xml: <extension point="org.eclipse.ui.perspectiveExtensions"> <perspectiveExtension targetID="org.eclipse.debug.ui.DebugPerspective"> <actionSet id="org.eclipse.cdt.dsf.debug.ui.updateModes"> </actionSet> </perspectiveExtension> </extension> HTH
Thanks Jonah! I just tried refreshing breakpoint view and it seems its broken when multiple breakpoints are present, there is an issue with collector in MIBreakpointsSynchronizer.doTargetBreakpointsSynchronized(..) which causes runtime exception.
I just tried a quick test case (GDB 9.2, Eclipse CPP 2020-12) and the refresh appeared to work (the breakpoints weren't actually out of sync though). Please file a new bug with some steps to reproduce, along with the exception and lets see if we can solve this.