I accidently messed up the default eclipse layout now I can't get it back the way it used to be. HERE is a picture. What really annoys me is that eclipse now is taking up unnecessary space at the top. What I want gone, but can't get rid of is the bar all the to the right with "Java" in it. Right clicking won't help at all. Second, I want to get rid of the bar left to this "Java"-bar. As you can see it doesn't really have ANY FUNCTIONALITY AT ALL(??). To get rid of this strange bar is the most important thing since this will move up "Java" and Quicksearch to the placement above.
Edit: Just so to be clarify, THIS bar is what I mean which woul solve everything.
Actually, the most helpful thing would be to restore the whole Eclipse layout to default. I have tried Window->Restore Perspective but it doesn't help me :(
Thanks!
right mouse click on the perspective(top-right "Java") and select Reset. This will fix the perspective.
EDIT: It seems to be a bug in Eclipse Juno. A suggestion is to delete the workbench.xmi file, but it doesn't work for everybody...
So If it doesnt work, you have to install your eclipse again.
There are different things you might try:
You should be able to drag and drop the bar to a location where it
automatically docks and does not disturb you (e.g. at the bottom)
Right click the emtpy bar and choose "hide toolbar"
If everything fails: Delete your eclipse installation and load a new one. Don't delete your workspace and point the new installation to your current workspace. You will have all your projects as they are now.
As a workaround, until this bug will be resolved, you can edit eclipse\plugins\org.eclipse.platform_4.2.1.v201209141800\css\e4_classic_winxp.css.
Append following code.
.MToolBar.Draggable {
handle-image: url(./winXPHandle.png);
}
.MToolControl.Draggable {
handle-image: url(./winXPHandle.png);
}
Source: https://bugs.eclipse.org/bugs/show_bug.cgi?id=389594#c4
I had to click on reset for all my perspectives, then exit eclipse, and re-open it. Worked for me.
When I'm trying to run my project it said that i have an errors in my project, but i can't see any. I have an Exclamation mark on my project. If I'm trying to run other project, it is run perfectly.
Before that happened, I played a little bit with the project library and tried to copy some jars to the library. I tried to copy the jars manual to.
Thanks!
did you try the "Problems" View? This should show additional information.
The easiest Way to get there:
Ctrl + 3, then type "Problems".
-Hannes
Besides the "Problems" view, there is also the Console that could give you some hints.
For the Console View, there is the problem that it can show different subviews; for example it can show the console for Android or the console for DDMS. In the toolbar at the upper right of the Console view, you will find the control to choose the right console to display. Be sure to choose the "Android Console".
Another possibility is to use the "Fix Project Properties" that you will find by right clicking on the projet => Android Tools -> Fix Project Properties. This will fixes some but not all the potential problems that you might have introduced in your project.
For the rest, check in detail all properties of the project.
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.
I am facing strange problem with eclipse [Ganymede]. Once I added some breakpoints in my code and now even after I delete all those breakpoints, it appears again when I start the eclipse.
So, regularly first thing what I have to do after starting the eclipse is manually delete all breakpoints to start working. Probably eclipse stores the information about these breakpoints in some file and, I think, if I will delete that file my problem might be resolved. Please let me know if you have some solution for this.
Another solution
Eclipse -> Run -> Remove All Breakpoints - for removing all Breakpoints for all Time
Eclipse -> Run -> Skip All Breakpoints - for temporary remove breakpoints
Perhaps it helps to check the Breakpoints view (Ctrl+3, type 'breakpoints') and see if they are inactive only or something. There, you can also deactivate them all at once (strikeout button).
You can go to debug prespective
and check or uncheck the desired breakpoint in the Breakpoints view
or show the view from the Window menu
Happened to me to. I think it's eclipse bug. I filed a bug for it, will update once there's progress on it.
I had a couple of "unable to load breakpoint" warnings which wouldn't go away, even after I deleted all breakpoints via the run->remove all breakpoints command. These were on "dead code" paths which had been abandoned for use in the present project.
Closing and re-opening eclipse made them go away.