How to I remove non-current Eclipse C++ launch configuration?
What I expect is, the RUN directly related to myproject.exe, not pointing to otherproject.exe sometimes. this is misleading and bring up error. So why not let the closed project with its launching configuration, i.e. closedproject.exe be invisible. And It should be automatically visible if I am editing that C++ code?
Yes I did check the menu setting (De-/Selected both tried):
Windows->Preference->Run/Debug->Launching->Launch Configurations:
Filter configuration in closed projects
Filter configuration inc deleted or missing projects
But the closedproject.exe still in the drop down list or sometime even link to current project build.
What did I wrong or what is the correct/clear setting for this? Or maybe pls. help me to understand why multiple project.exe are listed there?
Or it is a Eclipse improve point?
Thanks to #howlger I have found more insights on the toolbar settings of Eclipse.
In general, Eclipse default toolbar lineup are overdone for beginners like me. It should be more concise and turn-up only needed thus more intuitive.
The "Launch Bar" makes it explicit and standing out. But those build/debug functions/buttons are already in basic toolbar set, thus would be redundant or even misleading if people click on the drop-down menu of "Launch configuration", which is also not clean & clear in principal.
For that reason, the Launch Bar could be disable (for beginners):
Preference=>Launching=>Launch bar | right panel=> uncheck
Enable the Launch Bar
The red-squared button of terminate could be useful while debugging and re-build, because the previous malfunctioning RUN & program could still resident in task manager thus prevent further build and turn-up permission error, There helps this "Terminate" button instead of restart Eclipse. BUT as said, this button also in basic toolbar set. But it is often shadowed by the out-standing Launching Bar :-).
It is also possible to fully customize the toolbar (and lock it):
Windows=>Perspective=>Customize Perceptive
Then choose the tool bar items to display.
For the issue of multiple historical "launching configurations", I will report to Eclipse.
I use Eclipse Neon under Windows 10.
I installed a plugin (MonjaDB) using Eclipse Market Place. As I didn't find the plugin to be very useful I uninstalled it using Help->About->Installation Details->Installed Software->Uninstall. Sadly, however, this didn't seem to fully remove the plugin.
I now have a small red square on the right hand side of my workspace in the shortcut toolbar. This cannot be removed using the close option. I went so far as to remove my installation of Eclipse and the .eclipse directory in my home area but after a reinstall the square is still there.
Presumably this means that it is somehow associated with the project in my workspace?? Does anyone have any ideas how to remove this annoying square?
EDIT:
I have noticed two things
The MonjaDB perspective is hanging around somehow and
If I press the little red square on the right it opens an empty tab in the tab set to the right (where mylyn sits) with the title of DB Tree but I cannot remove it.
I have added three screen shots
MonjaDb perspective Partly Active
It seems like your current perspective is the one that was uninstalled. Just try opening a new one via the Open Perspective toolbar button that's close to thevred square, and then you can try right-click > Close on the red square.
At least a part of this is intentional...when the implementation class of a view no longer exists we leave the view 'open' but are supposed to show an "Error Part'. The reason to leave it up is to handle cases where a user has installed a new eclipse and opens his old workspace before installing the extensions. If we were to remove the views the user would have to set up their perspectives again once they had installed the extension.
Note that resetting the perspective won't work because the class implementing IPespectiveFactory no longer exists.
Closing the perspective and opening a new, different, one should work. If the perspective you open has visible views that are no longer available you should just close them.
I'm having one issue on Mac OS X El Capitan with Eclipse Mars and menu windows. When a menu window opens a new window, it shows in the back of the first one, and moves along with it (if I move the first one, the second one moves with it, but not the other way around). So there are two possible scenarios. If the second window shows a bit (like in this image), you still can move it and then interact with it, but if the second window is totally hidden (like this one when clicking 'Advanced'), then there's nothing you can do, since it seems impossible to put it on top. Is this a known bug or is there a solution for it?
Eclipse bug 478975 is open for this problem.
The problem only occurs when Eclipse (or any Eclipse RCP) is in full-screen mode. It works normally when not full-screen.
Update: A fix for this bug is included in Eclipse Neon (4.6) Release Candidate 3.
Eclipse 3.5.2 is not stopping in breakpoints. It's as if the debugger is using an older version of the source file.
Tried the usual refresh, clean all projects, build all, with no change.
Already in debug mode and the break point is checked.
*ok ended up deleting the whole project and checking it out again. but still curious what the issue was.
Perhaps you have pushed the Skip all Breakpoints button in the Breakpoints view.
Thanks guys, this really saved my day too.
I antecedently pressed on skip break points, if you did the same this will result on break point appearing with a backslash icon on them.
To bring it back to normal:
Switch to Debug perspective.
press on the breakpoints view tap -->> upper right hand corner of the screen, you also can go there by Window->show view-> breakpoints.
5th icon from the left you will see break point with backslash. press on that one.
To confirm, try putting break point on any line, and it should appear normally.
Press Ctrl + Alt + B
OR go through below steps
Clearing all Breakpoints fixed the issue
(within debugger perspective: Window -> Remove All Breakpoints).
Rebuilding the project did not work for me.
Sometimes you do start the debug mode but the debugger doesn't actually get attached/gets detached. I've also had this issue a few times when my laptop was reacting really slowly.
A reboot always solved it for me.
Also try doing a clean all (works miracles in Eclipse).
Please un check this from the Eclipse Menu.
Run->Skip all breakpoints.
I think this will be enabled permanently once You select the Remove all Break points option in the Debug/Breakpoints window.
Performing a "Clean All" worked for me.
Click on "Project" tab --> "Clean" menu-item.
In the "Clean" dialogue-box select "Clean all projects" radio-button. Leave the remaining values as default. Click "OK" button.
BINGO!!!The remote-debugging started working for me as beautiful as before.
It has also happened to me, in my case it was due to the GDB launcher, which I needed to turn to "Legacy Create Process Launcher". To do so,
either change the default launchers to the "Legacy Create Process Launcher", in Windows>Preferences>Run/Debug>Launching>Default Launchers.
or choose this launcher in the debug configuration of your application (Run>Debug configurations>choose your debug configuration). Under the "main" tab at the bottom, click on "Select other...", check the box "Use configuration specific settings" and choose "Legacy Create Process Launcher".
I had a conditional break point wrongly put on the method entry point. Removed that breakpoint and it worked.
Note: Tried Skip all Breakpoints, Clean all projects, Refresh, close Eclipse with no luck before nailing it.
In my case, somehow the breakpoints got automatically disabled because of this switch turned on, skip breakpoints.
Breakpoints have seemed to work and not-work on the versions of Eclipse I've used the last couple years. Currently I'm using Juno and just experienced breakpoints-not-working again. The solutions above, although good ones, didn't work in my case.
Here's what worked in my case:
deleted the project
check it back out from svn
import it into Eclipse again
run "mvn eclipse:eclipse"
Since the project is also a Groovy/Http-bulder/junit-test project, I had to:
convert the project from Java to Groovy
add /src/test/groovy to the Java Build Path (Source folders on build path)
include "**/*.groovy" on the Java Build Path for /src/test/groovy
I had all breakpoints enabled and configured as I should. But whenever I clicked "debug" it would only step through the program (press f5/f6) Turns out there was a rogue setting
Right Click project > debug configurations > "Debugger" tab > uncheck "Stop on startup at:" box
One reason for this situation can be, that you have pressed 'skip all breakpoints', when play- and another pictures are smaller than those normally are (because of higher resolution screen). Another thing can be, that break points are stopped only under VM threads, not under normal threads!
Go to (eclipse-workspace)\.metadata\.plugins\org.eclipse.wst.server.core and delete all tmp folders.
Clean and Restart server.
In my case I had to enable then disable an option in the Preferences.
I don't prefer the debug view to keep jumping when a breakpoint is hit so I disabled this option, but caused the issue in question.
The solution was to enable it again, start a debug session, the breakpoint is hit and shown in the UI, then disable again the option.
Looks like a bug in Eclipse 4.17
UPDATE
There is also another simpler way that will make Eclipse show the debugging highlight at the breakpoint or rather refresh the debugging UI to work as it should. After the breakpoint is reached, Eclipse will ask you to switch to debugging mode if you are not already in, click switch button, then activate the debug tab/view, you will notice that the stepping buttons are activated and the breakpoint line is highlighted.
First remove all 'toggle breakpoints' from the class file.
Then Eclipse requires a restart.
Then make sure 'Skip All breakpoints' is NOT enabled. If it is, make it disabled.
Then, add toggle breakpoint to the lines in your file and run on Debug mode.
A pop-up window must appear to confirm if you really want to Switch to debug mode. Say Yes and proceed.
I suddenly experienced the skipping of breakpoints as well in Eclipse Juno CDT. For me the issue was that I had set optimization levels up. Once I set it back to none it was working fine. To set optimization levels go to Project Properties -> C/C++ Build -> Settings -> Tool Settings pan depending on which compiler you are using go to -> Optimization and set Optimization Level to: None (-O0).
Hope this helps! Best
I had the same problem, and I found the real cause.
I had written some concurrent / multi-threads code, while I added some breakpoints inside the code running in a new thread. So, when JUnit tests ran over, and stopped soon, the code will not reach and stop at the breakpoints.
For this situation, we have to click and select "Keep JUnit running after a test run when debugging" check box at "Debug Configurations..."
switching workspace worked for me.
Go to File > Switch Workspace and choose different folder (workspace)
That's it and BINGO! Debugging started working for me as beautiful as before.
go breatpoint and click on 5th to eclipse->window>->show view->other->debug->breakpoint and click on 5th option (Skip All Breakpoints)
Make sure, that you are using the correct JRE version to debug your project. Especially if it's a third party project.
Also make sure, that there is no trigger point set for any breakpoint.
I had the same problem when I was using Eclipse Juno.. I installed Eclipse Indigo and it works fine. Try to reinstall eclipse.
A different solution worked for me. I also faced the same problem - debug points were not being updated, though they are shown correctly in the IDE editor and in Break Points tab.
My problem and solution are: While creating the project, the 'Default Output Folder' points to different location. At a later stage, I have mavenized the project, selecting "Project Right Click - Configure - Convert to Maven Project". So there are two sets of output folders exist in my project file system. Cleaning the project multiple times did not solve my problem. In the background it was pointing to different binary files. Finally, when I removed the Maven Feature and cleaned the project, this time everything worked fine. Env: Eclipse Juno and JRE is J2SDK 1.5.
I get all breakpoints skipped and marked as warnings when using -O2 in the compiler flags. Switched to -O0 -g in my makefile and breakpoints now work. Hope this helps.
If it doesn't stop even after unchecking SKIP ALL BREAKPOINTS, you can add this android.os.debug.waitfordebugger just before your breakpoint.
If you do this,your app will definitely wait for debugger at that point everytime,even if you are just running your app,which it will only find when your device is connected to eclipse.
After debugging you must remove this line for app to run properly or else android will just keep waiting for the debugger.
Try to restart eclipse, that works sometimes. I guess there is some kind of cache there.
In my case the debugged code in JBoss was older than the code in the Eclipse project. Rebuilding the .war solved the problem.
Facing same problem with Eclipse Luna.
Project clean didn't work.
Rebuild didn't work.
What makes it work is uninstall the app on the device before each debugging.
I use the Eclipse FileSync plugin for live remote debugging. Make sure you tick Allow different target folders & edit the Target folder file setting in the tree view.
Setting the Default target folder by the Browse... button without Allow different target folders will set all folders to the same target (I had both libs & classes set to the default for libs so my breakpoints did not update).
Since Eclipse 4.7/Oxygen released in June 2017, there is a new concept of "Triggers for breakpoints", which is displayed as a small "T" next to the breakpoint "blue bullet" icon.
All the other breakpoints that are initially suppressed by triggers
will be hit only after any of the trigger points has been hit. All the
triggers are disabled after a trigger point is hit and will be
re-enabled after the run.
In order to reset all the "trigger" flags, you need to do the following steps :
Switch to Debug perspective.
Right-click in the "Breakpoints" view
Select "Remove All Triggers".
Note : this step does not delete all your breakpoints, which occurs when selecting "Remove All" in the same contextual menu.
Note : the keyboard shortcut to enable the triggers is "Alt-R", which takes precedence on the shortcut to open the "Run" menu with its mnemonics, when the "Breakpoints" view is selected.