Related
I am experiencing an issue with Eclipse's toolbars (Eclipse Neon) - most of them are not visible and I don't know how to show it. I even tried to reinstall Eclipse, but (I don't exactly remember) either it did not help at all, or it did, but Eclipse had crashed once and toolbars disappeared again.
The perspective bar is missing, so is the Run toolbar and I think a few others as well. This is how it looks:
screenshot
Toolbars broke after the update to Neon, before that no problem existed.
Something quite strange has happened: The whole Eclipse main window disappeared while I was debugging a Play Framework project. The Eclipse symbol in the applications bar still shows up as usual (from where I still can force Eclipse to quit).
My System (Ubuntu 14.04.) still behaves as if Eclipse was there, e. g. other applications get unfocused when choosing Eclipse in the applications bar. Meanwhile I have re-started Eclipse (that didn't help) and even re-started Ubuntu (still the same behaviour).
When I start Eclipse the workspace selection window shows regularly up. If I select another workspace, it also shows up regularly (I have created a second one to test that). Eclipse even still reacts properly on any shortcut as well as well as F10 & F11. It seems like the Eclipse main application window was "transparent". Therefore I assume that it is a problem of Eclipse resp. its workspace rather than an Ubuntu problem.
Does anybody have an idea where to maybe re-configure the workspace? Or is there even a secret function for all that?
Thanks a lot!!
Meanwhile I was able to re-get the window: I clicked on a shadow effect that sometimes showed up. I resized that shadow with my mouse. As an effect the Eclipse window top bar (the one above the menu) showed up again. Afterwards I could "pull out" the window from the bar - and there it all was again... But I have still no idea, how that happened - and what might be the solution if someone runs into that issue without having a shadow.
I am having a problem in Eclipse where it freezes whenever I add a period (to try to bring up the content assist popup with possible methods). I can move the mouse, but the blinking text cursor disappears, I can't switch tabs or save, and I need to use a task manager to close Eclipse. This happens with all Java projects/files.
I have never had a problem like this with Eclipse before, and can't tell what started it. After doing several Google searches, all I found was this bug. However, I don't see a solution and am running Windows 7, not Linux. Also, I have never heard of Xulrunner. Does anybody have a solution or explanation? Is it an Eclipse setting, or a problem with my computer?
Error Log: https://dl.dropboxusercontent.com/u/101364250/eclipse_freeze.log
When I watched the error view, it seemed to output "Unhandled event loop exception" a lot.
For now, I have disabled the content assist, which seems to fix the problem.
However, this feature is very helpful, so any answers are appreciated!
Try opening Preferences and tick "Suspend all validators".
Try disable the hovers feature:
eclipse menu: Wndow > Preference
I am using Helios on Mac Snow Leopard. I don't know why but all of a sudden my arrow keys and delete button start not working only on Eclipse (so Eclipse ignores them) but the rest of the buttons works just fine. There is no exception/error thrown anywhere on the screen. I don't exactly know how to reproduce this malfunctioning.
All I can say, I am having exactly the same problem with this guy down here. Bad thing about it, the post sent in year 2002:s
Is there any one of you having the same issue? Any suggestions?
Edit:
Please mark "me too" on this bug report hoping that it will be fixed soon.
I was able to "restore" arrow and backspace keys by "Refreshing" the project.
UPDATE: 7/11/2017 I've not had this problem reoccur in a couple of years now. Either Eclipse fixed the problems or a more recent version of Mac OSX has fixed something. For the record I'm running Eclipse 4.5.2 on OSX 10.11.6.
UPDATE: 4/29/2011 Now it looks like this is not a Workspace or keyboard preferences issue at all. This just happened again but restoring from older Workspaces did not fix the issue. I finally had to reboot my Mac which seemed to resolve things. I'm going to try a restart in the future immediately if I see this again. I've submitted this bug with Eclipse. Please add a "me too" comment to the bug if it has not been fixed and you can reproduce this on your system.
I also have heard that on Macs, you can solve this by getting the unit to sleep either by closing the laptop lid or pulling the Apple menu down to sleep, wait a few seconds, and then starting it again. I've not tried this yet.
BTW, when this happens refreshing and other mechanisms have not worked.
UPDATE: 4/13/2011 Although the below instructions did fix my keyboard issues, I discovered other problems with my configuration and was finally forced to recover my Workspace from backups.
NOTE: This is not recommended but is here for information purposes. Typically these keys are handled by the native widget and are not defined.
So I just had the same problem under Eclipse 3.6.2.r362 on Mac OSX 10.6.7. Delete to the left and arrows not working. They worked in other applications. Option-Arrows worked fine to move a selection around. Arrows worked in the keyboard preferences window. Switching to another application and back didn't work. Restarting eclipse made no difference. Switching keyboard schemes from Emacs -> Default -> Emacs didn't work. Pressing all of the modifier keys did nothing. I tried all of the following and nothing works: Rebuilding the project, refreshing the source, restarting Eclipse.
Finally, I was able to fix this by going to the Preferences -> General -> Keys and resetting each of the bindings for the following keys. The bindings for each of the keys were blank.
Delete Previous to backspace
Line Up to up arrow
Line Down to down arrow
Previous Column to left arrow
Next Column to right arrow
This worked but then I noticed that all of the emacs key bindings were screwed. I thought they worked before so I'm not sure when this happened. I had to restore default key bindings (after writing down the ones that I had customized) and then restore my customized settings.
Makes me wonder what other key bindings have been reset and what did it. Frustrating but at least I can get back to coding.
If you see the same symptoms on Eclipse Windows, just press all your mouse buttons (including the wheel if you have one) at the same time together, and that seems to fix it.
Same weird problem, this worked for me: I just figured out that if I switch editor and then back again, backspace starts working again. (source)
For me, the root cause was my mouse.
Backspace and navigation keys did not work. I could fix this temporarily by manually setting the key bindings as described on this page.
The root cause and permanent solution was fixing the stuck 3rd mouse button on my Evoluent Vertical Grip mouse. Since I never used that button, I didn't notice that it was permanently engaged, probably from the mouse sliding off the desk on to the ground one too many times. Once I was able to get the button unstuck, the problem was solved immediately.
This was really frustrating. I spent weeks wondering why it was happening and sporadically searching the web for answers. Of course I had a temporary solution, but the fact that it kept happening was annoying. I tried reinstalling Eclipse from scratch, trying different versions and switching workspaces, but nothing worked. I'm surprised it ended up being a stuck mouse button after all that.
Also check that someone has not installed the vrapper plugin so that Eclipse accepts vi/vim like commands. If this is the case pressing i allows you access the editor window. If you are unaware that a work college has installed it (glares at someone) it can be a right $%#&$#! If installed there will be a V icon in the top toolbar. This plugin can be removed by going to the directory where Eclipse is installed in a term window and running
find . -name '\*vrapper\*' -exec rm -rf {} \;
It is that or tax you brain but supposedly increase your productively by learning all the Vim commands. Hope this helps someone...
In Windows and Linux environments I have experienced such issues when the system believes a modifier key is pressed. By pressing and releasing all modifier keys the issues often perish. However, on OSX I did not experience such issues, so this might be entirely wrong.
If the simple idea does not solve the issue, you could try to start a new workspace to see whether some preference causes the issue; or you could download a new Helios instance to check whether its working. I know, these are all serious issues, but may locate the problem.
Otherwise, you shall take a look at the question asked not long ago about keyboard issues, maybe there is some hint how to solve it.
I had the same problem with the "Delete" key in Eclipse 3.7.0 on Windows Vista. Suddenly the key stopped working and I couldn't figure out why. Recently I found a way to fix it when the problem occurs - it works for me every time:
In a code editor window in Eclipse, hoover on some method or variable or what have you, until the popup window appears with "Press 'F2' for focus" in the lower right corner. Click the popup window to switch focus, then click the editor window again so the pop-up disappears, and voilà, the Delete key works again.
Had this same issue. Turned out to be my middle button on my wireless mouse being pushed in my laptop bag. Normally I turn my mouse off, but this time I forgot. Glad that other people had this problem, otherwise I'd still be looking for the cause.
I have encountered this problem for years. It happens so infrequently however, that I almost always forget what I did to solve it. Restarting fixes it most of the time i think, and a few times "refreshing" worked, but nothing works 100% of the time.
In any case, someone on the bug report suggested just putting MacBook in Sleep cycle. This worked like a charm for me, so putting it out there for future reference.
https://bugs.eclipse.org/bugs/show_bug.cgi?id=344290#c24
Incidentally, I have experienced similar behavior with other applications, in particular Firefox. My thought is that it has to do with key bindings in general, and any application that provides overrides for defaults in the OS (this is a pretty huge assumption, so take with a correspondingly large grain of salt). I have also had this happen to me in Xcode, but a simple restart of the application fixes, whereas with Eclipse that wasn't sufficient most of the time.
Using eclipse JUNO on Win XP I also experience this issue.
Restarting the workbench using File > Restart does not work, but closing eclipse and starting again with -clean at the command prompt the keys start functioning again, without restart windows.
Note - Just found this fix elsewhere - you can fix this on Mac OSX by force-killing finder. That worked for me perfectly. Didn't need to restart!
For some odd reason, opening the preferences window and closing it right away, solves this problem for me (other solutions here didn't work).
Just in case this helps someone... I accidentally got things working again by doing the following:
Opened the offending file from the command line (I used 'vi').
Made the edit I wanted to make and saved the file.
Went back into Eclipse to refresh and redeploy my app.
As soon as the editor (this was a JSP file, btw) refreshed, I once again had full use of arrow, delete, etc.
YMMV
Jack
MacBook Pro 10.6.8, Eclipse Helios all of a sudden delete and arrows no longer work. Reboot worked for me.
I am also facing the same problem. In my case only the delete key is not working. I am using eclipse helios in ubuntu. The solutions given here are not working. However, restarting solves the issue.
I have the suspicion that this happens after updating Java on my Mac. So after updating Java it seems to be a good idea to reboot the machine always.
I got this same problem when I started using JRobot. In one piece of code I pressed the mouse but did not release. By releasing the mouse in a later piece of code I managed to solve the issue. You can recreate this problem using the code below. Release the mouse button to solve the issue.
Robot robot;
try {
robot = new Robot();
robot.mousePress(InputEvent.BUTTON2_MASK);
//robot.mouseRelease(InputEvent.BUTTON2_MASK);
} catch (AWTException e1) {
// TODO Auto-generated catch block
e1.printStackTrace();
}
Pressing left and right mouse buttons simultaneosly multiple times worked for me.
Using eclipse Luna (4.4) on Redhat and viewing via Xming (Windows 7, 64-bit), I could not use backspace, arrows, delete or even enter, but alphanumeric worked. This problem was not intermittent, but always there from the start. For me, I found that setting a break-point in the code, running and allowing eclipse to switch perspectives fixed it every time. Hope it helps someone else as the above suggestions (ie switching editors, changing key mappings, refreshing and restarting eclipse) did not work for me.
One interesting diagnostic of the problem I had was that going to the screen where you change the key-mappings, I was able to use the delete key. But not in java files or untitled text files.
WORKED!!!
I'm using Eclipse Luna and Windows 7, but guess it works in all kinds as well.
In Eclipse, go to tab Window->preferences->General->keys
Then, find the Command "Delete" and "Delete Previous" in the list, and check if
they are assign with something or not. If it is assign with the wrong key, click in "Unbind Command".
Just select the command that you want to change and press the key that you want to be on the "binding" field.
I think it works for Next, Next Column, Previous, Previous Column, Line Up, Line Down, or whatelse you want!!
Had, similar problem with not working “enter” and “delete”, none of above methods helped me – to fix problem I had to switch to default java formatter (one I was using somehow stopped working)
For me it was that the keyboard layout accidentally changed to vietnamese language and there are inherent key mapping combinations that create trouble when editing.
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.