Use org.eclipse.debug.ui.contextViewBindings for 'org.eclipse.cdt.visualizer.view' and 'org.eclipse.cdt.debug.ui.executablesView' views. #918
Comments
raghucssit
added a commit
to raghucssit/cdt
that referenced
this issue
Oct 19, 2024
and Executables Views. Similar to Memory View and Debug Console View, We can use org.eclipse.cdt.debug.ui.debugging for Visualizer and Executables Views see eclipse-cdt#918
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
raghucssit
added a commit
to raghucssit/cdt
that referenced
this issue
Oct 19, 2024
and Executables Views. Similar to Memory View and Debug Console View, We can use org.eclipse.cdt.debug.ui.debugging for Visualizer and Executables Views see eclipse-cdt#918
Ok sure. Thanks. |
jonahgraham
pushed a commit
that referenced
this issue
Oct 22, 2024
and Executables Views. Similar to Memory View and Debug Console View, We can use org.eclipse.cdt.debug.ui.debugging for Visualizer and Executables Views see #918
|
Completed in #919 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The problem is when the eclipse switches to
Debugperspective 'org.eclipse.cdt.visualizer.view' and 'org.eclipse.cdt.debug.ui.executablesView' views are populated by default. Irrespective of debug context.If we debug java application these views are not needed. So we can bind them to
contextId="org.eclipse.cdt.debug.ui.debugging".Already many views like
Memory ViewandDebug Console Vieware using this approach.We can use same approach to
Visualizer ViewandExecutable View.It looks like below when i try to debug Java application there is no CPP project in the workspace.
The text was updated successfully, but these errors were encountered: